[ http://jira.codehaus.org/browse/MNG-2191?page=all ]
Brett Porter closed MNG-2191:
-----------------------------
Assign To: Brett Porter
Resolution: Won't Fix
please use <dependencyManagement> to assign a global version.
> [Dependencies] Override parent dependency scope without specifying version
> --------------------------------------------------------------------------
>
> Key: MNG-2191
> URL: http://jira.codehaus.org/browse/MNG-2191
> Project: Maven 2
> Type: New Feature
> Components: Dependencies
> Versions: 2.0.2
> Reporter: Jacob Robertson
> Assignee: Brett Porter
> Priority: Minor
>
>
> In my parent pom, I have log4j listed as a runtime dependency (since log4j is
> discovered by commons-logging). In the child pom, it turns out that I need
> to depend on it with compile scope (since I have a custom appender). My
> issue is that I want to minimize the maintenance of these poms, so I'd prefer
> if the child pom didn't have to specify what version of log4j it depends on.
> However, if I take out the version element I get "Project build error Failed
> to validate POM" (In the Eclipse maven2 console). What I'm looking for is
> something like this
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <scope>compile</scope>
> <versionInheritedFromParentPom>true</versionInheritedFromParentPom>
> </dependency>
> You get the idea...
--
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
