[jira] Updated: (MNG-3825) Dependencies with classifier should not always require a version.

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-3825:
------------------------------

    Fix Version/s: 2.x

could consider this with dependency grouping discussion for an alternate POM format

> Dependencies with classifier should not always require a version.
> -----------------------------------------------------------------
>
>                 Key: MNG-3825
>                 URL: http://jira.codehaus.org/browse/MNG-3825
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Dependencies
>            Reporter: Paul Gier
>             Fix For: 2.x
>
>
> If I have two dependencies one with a classifier and one without, that look something like this:
> {code:xml}
> <dependency>
>   <groupId>com.mycompany</groupId>
>   <artifactId>project1</artifact>
>   <version>1</version>
> </dependency>
> <dependency>
>   <groupId>com.mycompany</groupId>
>   <artifactId>project1</artifact>
>   <classifier>client</classifier>
>   <version>1</version>
> </dependency>
> {code}
> Currently I need to specify versions for both of them.  If I specify the versions in dependency management, I should only have to specify the non-classifier version.  The dependency with the classifier should default to the same version as the one without the dependency.  This would save a lot of extra configuration for some projects.

-- 
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