You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2008/11/07 22:28:13 UTC
[jira] Created: (MNG-3825) Dependencies with classifier should not
always require a version.
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
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
[jira] Updated: (MNG-3825) Dependencies with classifier should not
always require a version.
Posted by "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: 3.1
> Dependencies with classifier should not always require a version.
> -----------------------------------------------------------------
>
> Key: MNG-3825
> URL: http://jira.codehaus.org/browse/MNG-3825
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Dependencies
> Reporter: Paul Gier
> Fix For: 3.1
>
>
> 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
[jira] Reopened: (MNG-3825) Dependencies with classifier should not
always require a version.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter reopened MNG-3825:
-------------------------------
on second thought, best to keep the request as is and look at it in context with the other issues :)
> Dependencies with classifier should not always require a version.
> -----------------------------------------------------------------
>
> Key: MNG-3825
> URL: http://jira.codehaus.org/browse/MNG-3825
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Dependencies
> Reporter: Paul Gier
> Fix For: 3.1
>
>
> 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
[jira] Closed: (MNG-3825) Dependencies with classifier should not
always require a version.
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-3825.
-----------------------------
Resolution: Won't Fix
Fix Version/s: (was: 2.x)
I'm going to say this is not something we'd do as stated, but probably a good piece of input to a more concise dependency format (eg, grouping as mentioned above). That's something to consider for 3.1.
If you disagree, we can reopen and work through it on dev@
> Dependencies with classifier should not always require a version.
> -----------------------------------------------------------------
>
> Key: MNG-3825
> URL: http://jira.codehaus.org/browse/MNG-3825
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Dependencies
> Reporter: Paul Gier
>
> 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
[jira] Updated: (MNG-3825) Dependencies with classifier should not
always require a version.
Posted by "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