You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org> on 2007/04/24 14:59:26 UTC

[jira] Closed: (MRELEASE-147) Version number for a dependency with ${pom.groupId} not updated in multi-module.

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

Emmanuel Venisse closed MRELEASE-147.
-------------------------------------

      Assignee: Emmanuel Venisse
    Resolution: Fixed

Fixed.

> 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
>            Assignee: Emmanuel Venisse
>            Priority: Minor
>             Fix For: 2.0-beta-5
>
>
> 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