You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "kristian meier (JIRA)" <ji...@codehaus.org> on 2007/03/15 19:15:36 UTC
[jira] Created: (MRELEASE-204) two dependencies with the same
groupId and artifactId can not be released
two dependencies with the same groupId and artifactId can not be released
-------------------------------------------------------------------------
Key: MRELEASE-204
URL: http://jira.codehaus.org/browse/MRELEASE-204
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Affects Versions: 2.0-beta-5
Environment: linux, maven2, java1.5/1.4
Reporter: kristian meier
Priority: Minor
Attachments: patch.txt
I have pom which has something like
<dependency>
<groupId>de.tipitaka</groupId>
<artifactId>utils</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>de.tipitaka</groupId>
<artifactId>utils</artifactId>
<version>1.0-SNAPSHOT</version>
<classifier>sources</classifier>
</dependency>
and the maven-release-manager only increases the version at the first of these dependencies.
the attached patch against the trunk of maven-release-manager fixes the problem and works with my porject.
--
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: (MRELEASE-204) two dependencies with the same
groupId and artifactId can not be released
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse closed MRELEASE-204.
-------------------------------------
Assignee: Emmanuel Venisse
Resolution: Fixed
Fix Version/s: 2.0-beta-6
> two dependencies with the same groupId and artifactId can not be released
> -------------------------------------------------------------------------
>
> Key: MRELEASE-204
> URL: http://jira.codehaus.org/browse/MRELEASE-204
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Affects Versions: 2.0-beta-5
> Environment: linux, maven2, java1.5/1.4
> Reporter: kristian meier
> Assignee: Emmanuel Venisse
> Priority: Minor
> Fix For: 2.0-beta-6
>
> Attachments: patch.txt
>
>
> I have pom which has something like
> <dependency>
> <groupId>de.tipitaka</groupId>
> <artifactId>utils</artifactId>
> <version>1.0-SNAPSHOT</version>
> </dependency>
> <dependency>
> <groupId>de.tipitaka</groupId>
> <artifactId>utils</artifactId>
> <version>1.0-SNAPSHOT</version>
> <classifier>sources</classifier>
> </dependency>
> and the maven-release-manager only increases the version at the first of these dependencies.
> the attached patch against the trunk of maven-release-manager fixes the problem and works with my porject.
--
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