maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacob Robertson (JIRA)" <>
Subject [jira] Created: (MNG-2191) [Dependencies] Override parent dependency scope without specifying version
Date Thu, 30 Mar 2006 13:44:48 GMT
[Dependencies] Override parent dependency scope without specifying version

         Key: MNG-2191
     Project: Maven 2
        Type: New Feature

  Components: Dependencies  
    Versions: 2.0.2    
    Reporter: Jacob Robertson
    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


You get the idea...

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