Provided means to include in the compile do but not in the package (war)
Optional means that it wont be pulled in transitively by users of your
jar
Sent from my iPhone
On May 9, 2008, at 4:12 PM, Paul Smith <[EMAIL PROTECTED]> wrote:
Could some explain the difference between the dependency scope
"provided" versus "optional" if there actually is any..
We have converted log4j over to Maven recently and accidently forgot
to mark a few dependencies with flags indicating that, while needing
for compile time, should not necessarily be enforced on the end user.
I refer people to this issue:
https://issues.apache.org/bugzilla/show_bug.cgi?id=43304
I originally used 'optional' because I saw this being used in the
ActiveMQ project, but now I can't find any real definitive reference
to what that means.
I've read:
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
and that makes no mention of the 'optional' scope type. Is it a
legacy marker?
If someone could provide advice here I would appreciate it.
cheers,
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
