this message in context:
http://maven.40175.n5.nabble.com/maven-enforcer-plugin-to-ban-a-transitive-provided-dependency-tp5752733.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users
this message in context:
http://maven.40175.n5.nabble.com/maven-enforcer-plugin-to-ban-a-transitive-provided-dependency-tp5752733.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users
Thank you Stephen!
Does anybody knows if there is already a plugin able to this?
David
PS: Guys don't publish unrelated posts on this thread.
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-enforcer-plugin-to-ban-a-transitive-provided-dependency-tp5752733p5752745
Hello,
My POM declares a dependency on a library that itself has dependency on JEE
apis (jca, jms) declared as provided.
Those dependencies are not set in my classpath by the eclipse plugin,
neither get include during compile.
According to
Hi Nicolas,
Apparently you have indeed missed a bit ;)
The URL you pasted mentions:
*provided* - this is much like compile, but indicates you expect the JDK or
a container to provide it. It is only available on the compilation
classpath, and is not transitive.
This means that they were needed
That right,
I don't want those javax.* jars to be bundled in my war.
according to maven doc :
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html,
It is expected to be transitive anyway.
2007/6/4, Jo Vandermeeren [EMAIL PROTECTED]:
Hi Nicolas,
Apparently
