You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ace.apache.org by "Geert Schuring (JIRA)" <ji...@apache.org> on 2011/02/23 02:25:38 UTC
[jira] Created: (ACE-120) Correct dependency scopes
Correct dependency scopes
-------------------------
Key: ACE-120
URL: https://issues.apache.org/jira/browse/ACE-120
Project: Ace
Issue Type: Sub-task
Components: Maven Build
Reporter: Geert Schuring
Fix For: 0.8.0
Make sure the parent pom does not set scope for dependencies, and let every module define non-default (compile) scopes of dependencies.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (ACE-120) Correct dependency scopes
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved ACE-120.
--------------------------------------
Resolution: Fixed
Assignee: Jean-Baptiste Onofré
Revision 1074917.
The dependencyManagement is now compile.
Each sub-modules can now override the scope as they want.
> Correct dependency scopes
> -------------------------
>
> Key: ACE-120
> URL: https://issues.apache.org/jira/browse/ACE-120
> Project: Ace
> Issue Type: Sub-task
> Components: Maven Build
> Reporter: Geert Schuring
> Assignee: Jean-Baptiste Onofré
> Labels: build, dependency, maven, scope
> Fix For: 0.8.0
>
>
> Make sure the parent pom does not set scope for dependencies, and let every module define non-default (compile) scopes of dependencies.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (ACE-120) Correct dependency scopes
Posted by "Geert Schuring (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999261#comment-12999261 ]
Geert Schuring commented on ACE-120:
------------------------------------
I'm working on this one. The idea is that the parent pom only defines the dependency versions in the dependencymanagement section and not the scope. A module developer can therefor always assume that a dependency he adds to his pom has scope=compile which is the default value. This is important because the behavior of a project becomes unpredictable if defaults like scope=compile are overridden in any parent.
> Correct dependency scopes
> -------------------------
>
> Key: ACE-120
> URL: https://issues.apache.org/jira/browse/ACE-120
> Project: Ace
> Issue Type: Sub-task
> Components: Maven Build
> Reporter: Geert Schuring
> Labels: build, dependency, maven, scope
> Fix For: 0.8.0
>
>
> Make sure the parent pom does not set scope for dependencies, and let every module define non-default (compile) scopes of dependencies.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira