[
http://jira.codehaus.org/browse/MNG-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153608#action_153608
]
Grzegorz Borkowski commented on MNG-3742:
-----------------------------------------
Yes you're right: artifactId and groupId were reversed. Very strange how did I
get to such configuration - too long time to remember it now. But in fact,
after fixing the pom, everything works.
> Exclusion of transitive dependiencies does not work
> ---------------------------------------------------
>
> Key: MNG-3742
> URL: http://jira.codehaus.org/browse/MNG-3742
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.9
> Reporter: Grzegorz Borkowski
> Attachments: pom.xml
>
>
> I create empty project with jar-type pom. I add dependency on log4j 1.2.15
> (the most up-to-date version). Build fails, because log4j declares in its pom
> dependencies on some Sun librareis, which are not available for Maven to
> download. They should be marked optional in log4j pom, but they are not (they
> claim it will be fixed in 1.2.16, but it is not released yet). So I exclude
> dependienices, according to the document:
> http://docs.codehaus.org/display/MAVENUSER/Dependency+Mechanism
> However, build still fails, as Maven still tries to download excluded
> libraries. This seems a bug in Maven.
> This is easilyt reproducable from comand-line, NetBeans or Eclipse.
> See my pom attached.
--
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
