maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason van Zyl (JIRA)" <>
Subject [jira] Closed: (MNG-2919) Scope defined in dependencyManagement section of parent pom overwrites scope of current artifact
Date Mon, 04 Jun 2007 18:27:59 GMT


Jason van Zyl closed MNG-2919.

    Resolution: Cannot Reproduce

I'm not really sure from your explanation with your example what you are trying to say is
happening. I'm using "mvn help:effective-pom" on the child POM and seeing the behavior I expect
where the junit dependency in the child overrides the scope of what is stated in the parent's
depMan element. The child wins as it should. The scope in the child is not overwritten in
your sample project. You need to explain better what you want me to look at or what the result
should be instead of describing the general and then giving me concrete example that is working
as expected.

> Scope defined in dependencyManagement section of parent pom overwrites scope of current
> ------------------------------------------------------------------------------------------------
>                 Key: MNG-2919
>                 URL:
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.0.6
>            Reporter: Joerg Schaible
>            Priority: Critical
>             Fix For: 2.0.7
>         Attachments:
> 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:
For more information on JIRA, see:


View raw message