maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain DeschĂȘnes (JIRA) <j...@codehaus.org>
Subject [jira] Created: (MRELEASE-147) Version number for a dependency with ${pom.groupId} not updated in multi-module.
Date Wed, 09 Aug 2006 15:25:09 GMT
Version number for a dependency with ${pom.groupId} not updated in multi-module.
--------------------------------------------------------------------------------

                 Key: MRELEASE-147
                 URL: http://jira.codehaus.org/browse/MRELEASE-147
             Project: Maven 2.x Release Plugin
          Issue Type: Bug
    Affects Versions: 2.0-beta-4
            Reporter: Sylvain DeschĂȘnes
            Priority: Minor


I have a multi-module project, project-A depends on project-B.

If I use in project-A :

		<dependency>
			<groupId>${pom.groupId}</groupId>
			<artifactId>project-B</artifactId>
			<version>1.0-SNAPSHOT</version>
		</dependency>

The version number is not updated when I do a release.

But with:

		<dependency>
			<groupId>com.real.group.id</groupId>
			<artifactId>project-B</artifactId>
			<version>1.0-SNAPSHOT</version>
		</dependency>

The release plugin updates it perfectly.

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

       

Mime
View raw message