[
http://jira.codehaus.org/browse/MNG-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98458
]
Patrick Schneider edited comment on MNG-2919 at 6/5/07 11:09 AM:
-----------------------------------------------------------------
I am able to reproduce the problem using the sample that Joerg attached. The
issue is not with junit, but with the child project itself (issue/pom.xml).
I believe this is an ArtifactCollector problem, probably introduced in the fix
to MNG-1577. It may take me a bit of time to figure it out, so maybe we can
slate this for 2.0.8?
was:
I am able to reproduce the problem using the sample that Joerg attached. The
issue is not with junit, but with the child project itself
(MNG-2919/issue/pom.xml).
I believe this is an ArtifactCollector problem, probably introduced in the fix
to MNG-1577. It may take me a bit of time to figure it out, so maybe we can
slate this for 2.0.8?
> Scope defined in dependencyManagement section of parent pom overwrites scope
> of current artifact
> ------------------------------------------------------------------------------------------------
>
> Key: MNG-2919
> URL: http://jira.codehaus.org/browse/MNG-2919
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.6
> Reporter: Joerg Schaible
> Priority: Critical
> Fix For: 2.0.8
>
> Attachments: MNG-2919.zip
>
>
> If the dependencyManagement contains also the current artifact with a scope,
> this scope will overwrite the scope of the current project.
> Use case: A global parent POM that defines the released versions of all
> artifacts. Those artifacts are all defined with "runtime" scope to enforce
> projects to declare compile time deps (workaround for MNG-2589) or some are
> declared with scope "test" since they should only be used in unit or it tests.
> Problem: If that artifact is build with M206, it does no longer compile.
> Reason: The declaration in the dependencyManagement section overwrites also
> the scope of the current artifact itself i.e. all the declared dependencies
> are suddenly also no longer in the compile scope.
> Solution: The dependencyManagement may not overwrite the scope of the current
> artifact.
> Workaround: Add for the current artifact in its own POM a
> dependencyManagement section where it is itself declared again with compile
> scope.
--
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
