[ http://jira.codehaus.org/browse/MEV-185?page=comments#action_50292 ]
Fabrice BELLINGARD commented on MEV-185: ---------------------------------------- Avalon, Logkit and Log4J are not required when using commons-logging. That's why they need to be set as "optional". And I read a post from Brett saying that if you want a dependency to be optional, you have to set <optional> tag to "true" (http://www.nabble.com/-m2-are-optional-dependencies-implemented--t396628.html#a1092315). I figured this out when I wanted to use commons-logging in my web app: I got all the three other JARs put in my WEB-INF/lib whereas I don't need them at all. Setting <optional> to true would disable the transitivity for those JARs that are not required for commons-logging - and I'm pretty sure that this is what the author of this POM wanted to do but he didn't knew that <optional> had to be set to "true" to make it work. > commons-logging-1.0.4 POM dependencies not using <optional> properly > -------------------------------------------------------------------- > > Key: MEV-185 > URL: http://jira.codehaus.org/browse/MEV-185 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Fabrice BELLINGARD > > > In the following dependency : > <dependency> > <groupId>avalon-framework</groupId> > <artifactId>avalon-framework</artifactId> > <version>4.1.3</version> > <optional/> > </dependency> > "<optional>true</optional>" should be used. > I haven't checked for the other versions of the artifact. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
