ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geert Schuring (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ACE-120) Correct dependency scopes
Date Fri, 25 Feb 2011 08:30:38 GMT

    [ 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

        

Mime
View raw message