Hi Sunil,
Firstly, this is not the right list to post this questions. This
question belongs to Maven Users List <[email protected]>
I don't think plugin dependencies will interfere with your project
dependencies? Is there any side effect of junit 3.8.1 being downloaded
on your packaging?
You can anyway try dependency:tree and make sure that none of your
project dependencies are downloading it. I don't think plugin
downloading a Junit dependency is any problem?
Thanks,
Kalpak
Hi,
In one of project application, I was using junit 3.8.1. Now I want to move
to junit 4.8.1. I have changed the pom dependancy for downloading junit
4.8.1 and it is working fine. But I am noticing that junit 3.8.1 is still
being downloaded by Maven through nexus repository. How do I avoid
downloading junit 3.8.1?
When I did “mvn –X clean”, it showed me the junit 3.8.1 is getting
downloaded may be because it is present as a dependency in the artifact
buildnumber-maven-plugin which is under group org.codehaus.mojo. To try
avoiding this, I went and changed pom of that artifcats and version found in
/org/apache/maven//maven-xxx.pom
But it is still downloading 3.8.1 when I do mvn clean. Here is the pom:
org.codehaus.mojo
buildnumber-maven-plugin
1.0-beta-3
validate
create
false
false
org.apache.maven.plugins
maven-compiler-plugin
1.5
1.5
org.apache.maven.plugins
maven-surefire-plugin
2.5
test
test
test
junit
junit
4.8.1
test
---
Thanks
Sunil
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
