You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joerg Schaible (JIRA)" <ji...@codehaus.org> on 2007/04/02 14:14:06 UTC
[jira] Created: (MNG-2919) Scope defined in dependencyManagement
section of parent pom overwrites scope of current artifact
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
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
[jira] Commented: (MNG-2919) Scope defined in dependencyManagement
section of parent pom overwrites scope of current artifact
Posted by "Patrick Schneider (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98640 ]
Patrick Schneider commented on MNG-2919:
----------------------------------------
Still need to port this up to the trunk -- will do so this evening or tomorrow.
> 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
> Assignee: Patrick Schneider
> Priority: Critical
> Fix For: 2.0.7
>
> 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
[jira] Issue Comment Edited: (MNG-2919) Scope defined in
dependencyManagement section of parent pom overwrites scope of current
artifact
Posted by "Patrick Schneider (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Closed: (MNG-2919) Scope defined in dependencyManagement
section of parent pom overwrites scope of current artifact
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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 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.7
>
> 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
[jira] Commented: (MNG-2919) Scope defined in dependencyManagement
section of parent pom overwrites scope of current artifact
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98464 ]
Jason van Zyl commented on MNG-2919:
------------------------------------
Is this something we can squeeze into 2.0.7?
> 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
> Assignee: Patrick Schneider
> 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
[jira] Commented: (MNG-2919) Scope defined in dependencyManagement
section of parent pom overwrites scope of current artifact
Posted by "Patrick Schneider (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98477 ]
Patrick Schneider commented on MNG-2919:
----------------------------------------
I will start work on it this afternoon. Like I said, I'm pretty sure where it's being caused, but I can't say for sure when I'll be done. I guess it depends on when you're looking to ship 2.0.7.
> 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
> Assignee: Patrick Schneider
> 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
[jira] Reopened: (MNG-2919) Scope defined in dependencyManagement
section of parent pom overwrites scope of current artifact
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl reopened MNG-2919:
--------------------------------
> 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.7
>
> 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
[jira] Updated: (MNG-2919) Scope defined in dependencyManagement
section of parent pom overwrites scope of current artifact
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated MNG-2919:
-------------------------------
Fix Version/s: 2.0.7
> 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.7
>
> 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
[jira] Reopened: (MNG-2919) Scope defined in dependencyManagement
section of parent pom overwrites scope of current artifact
Posted by "Patrick Schneider (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Schneider reopened MNG-2919:
------------------------------------
> 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
> Assignee: Patrick Schneider
> 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
[jira] Commented: (MNG-2919) Scope defined in dependencyManagement
section of parent pom overwrites scope of current artifact
Posted by "Patrick Schneider (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100919 ]
Patrick Schneider commented on MNG-2919:
----------------------------------------
Added fix to the trunk.
> 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
> Assignee: Patrick Schneider
> Priority: Critical
> Fix For: 2.0.7
>
> 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
[jira] Closed: (MNG-2919) Scope defined in dependencyManagement
section of parent pom overwrites scope of current artifact
Posted by "Patrick Schneider (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Schneider closed MNG-2919.
----------------------------------
Resolution: Fixed
See MNG-2931 for more information. Fixing this bug was a matter of removing the version check from that fix. Basically we don't want to alter the originatingArtifact at all when it's being built. Added unit test the mimics the attached example project.
> 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
> Assignee: Patrick Schneider
> Priority: Critical
> Fix For: 2.0.7
>
> 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
[jira] Updated: (MNG-2919) Scope defined in dependencyManagement
section of parent pom overwrites scope of current artifact
Posted by "Joerg Schaible (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joerg Schaible updated MNG-2919:
--------------------------------
Attachment: MNG-2919.zip
Simple setup to demonstrate the problem.
> 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
> 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
[jira] Updated: (MNG-2919) Scope defined in dependencyManagement
section of parent pom overwrites scope of current artifact
Posted by "Patrick Schneider (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Schneider updated MNG-2919:
-----------------------------------
Fix Version/s: (was: 2.0.8)
2.0.7
> 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
> Assignee: Patrick Schneider
> Priority: Critical
> Fix For: 2.0.7
>
> 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
[jira] Updated: (MNG-2919) Scope defined in dependencyManagement
section of parent pom overwrites scope of current artifact
Posted by "Patrick Schneider (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Schneider updated MNG-2919:
-----------------------------------
Fix Version/s: (was: 2.0.7)
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
> Assignee: Patrick Schneider
> 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
[jira] Commented: (MNG-2919) Scope defined in dependencyManagement
section of parent pom overwrites scope of current artifact
Posted by "Patrick Schneider (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98458 ]
Patrick Schneider commented on MNG-2919:
----------------------------------------
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.7
>
> 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