how to configure maven to add junit 4.10 instead of 3.8 dependency in new project

Question

When i am creating a new maven project in eclipse kepler, eclipse automatically adds junit 3.8 dependency in pom.xml like

<dependency>
    <groupId>junit</groupId>
    <artifactId>junit</artifactId>
    <version>3.8</version>
    <scope>test</scope>
</dependency>

I want to be available newer version like: 4.10,

Where can i configure to use newer version instead of old?

@adarshr I am using eclipse kepler service pack 1, i think this version is the latest. — Abhishek Nayak, Feb 14 '14 at 10:47
why not to change the dependency version manually? from 3.8 to desired version. — jelies, Feb 14 '14 at 11:03
@jelies instead of changing manually by me, i want to do that for me by eclipse. — Abhishek Nayak, Feb 14 '14 at 11:05
@Rembo oh I see. An option could be create the new maven project based on an archetype that uses this junit version. — jelies, Feb 14 '14 at 11:10
possible duplicate of [create POM with junit 4](http://stackoverflow.com/questions/14505377/create-pom-with-junit-4) — František Hartman, Feb 14 '14 at 11:16
@frant.hartm the solution i have to use command prompt, am looking for solution using eclipse new maven project wizard. — Abhishek Nayak, Feb 14 '14 at 11:25

score 9 · Accepted Answer · edited May 23 '17 at 11:33

9

The junit version is described in archetype that is used to create maven project.

You need to either find archetype that will fit your needs, or create your own.

Then once you have it you need to select to use this archetype when creating the project in Eclipse.

edited May 23 '17 at 11:33

Community

answered Feb 14 '14 at 11:33

@frant.hartm Why even now the default JUnit version in Eclipse Maven archetype is 3, not 4 whcih seems to be current? – Line Sep 04 '18 at 12:20

score 3 · Answer 2 · answered Feb 14 '14 at 11:48

It's pretty common to have a company/product wide version of one of the following: -

A common parent pom with a dependency management section controlling all your versions
A common pom which is included as a dependency and imports all the testing dependencies, e.g., my-company-test. That can either include your common test code as well or be of type pom and just act as a dependency vacuum.
An archetype (as frant.hartm says) which defines all of your common dependency versions up front.

I would personally go with both the dependency based pom and an archetype which imports it.

You can always override versions if you need too.

score 1 · Answer 3 · answered Feb 14 '14 at 14:45

You have to state the version that you want in the dependency, for example I use JUnit 4.11 in Eclipse Juno:

<dependency>
   <groupId>junit</groupId>
   <artifactId>junit</artifactId>
   <version>4.11</version>
   <scope>test</scope>
</dependency>

So you need to set your version to 4.10 or whatever version there is that you desire.

3 Answers3