[
http://jira.codehaus.org/browse/MNG-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260166#action_260166
]
Emmanuel Hugonnet commented on MNG-5041:
----------------------------------------
Yes, Silverpeas poms on github ;)
)After more investigations using the latest help plugin and effective pom all
is working fine.
It seems to come from a bug in the assembly plugin (2.2beta5) which was fixed
in 2.2.1.
The fact that the dependency plugin display wrong informations lead us to
creating this bug.
Sorry for the inconvenience.
> Scope of dependecies defined in Dependecy Management can't be overriden
> -----------------------------------------------------------------------
>
> Key: MNG-5041
> URL: http://jira.codehaus.org/browse/MNG-5041
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.0.2, 3.0.3
> Environment: Linux x64 JDK 1.60_24
> Reporter: Emmanuel Hugonnet
> Assignee: Benjamin Bentmann
> Priority: Blocker
> Attachments: MNG-5041.zip
>
>
> If I define a dependency with in a parent pom using dependency management I
> can't override the scope of the dependency management declaration in a child
> pom.
> If I use the dependency plugin the tree is as expected (the child override
> the parent) but if I use the effective-pom I get what is declared in the
> dependency management.
> This seems a Maven 3.0.x bug
--
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
