You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Martin von Zweigbergk (JIRA)" <ji...@codehaus.org> on 2008/06/09 18:24:12 UTC
[jira] Created: (MRELEASE-354) Versions defined in profiles are not
updated
Versions defined in profiles are not updated
--------------------------------------------
Key: MRELEASE-354
URL: http://jira.codehaus.org/browse/MRELEASE-354
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-7
Environment: Maven version: 2.0.9
Java version: 1.6.0_06
OS name: "windows 2000" version: "5.0" arch: "x86" Family: "windows"
Reporter: Martin von Zweigbergk
Versions defined in profiles (in either <dependencies> or <dependecyManagement>) should be updated, regardless of which profile are active.
--
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] Commented: (MRELEASE-354) Versions defined in profiles are
not updated
Posted by "Mathias Arens (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157822#action_157822 ]
Mathias Arens commented on MRELEASE-354:
----------------------------------------
To solve this issue would it be a good idea to extend the
{{org.apache.maven.shared.release.phase.GenerateReleasePomPhase.createReleaseModel()}}
routine? I would iterate over the list of profiles and rewrite the profile dependencies there. Is this a possible solution?
{code:java}
private Model createReleaseModel( MavenProject project, ReleaseDescriptor releaseDescriptor, ReleaseEnvironment releaseEnvironment,
List reactorProjects, ReleaseResult result )
throws ReleaseFailureException, ReleaseExecutionException
{
Map originalVersions = getOriginalVersionMap( releaseDescriptor, reactorProjects );
Map mappedVersions = getNextVersionMap( releaseDescriptor );
MavenProject releaseProject = new MavenProject( project );
Model releaseModel = releaseProject.getModel();
...
// rewrite dependencies
releaseModel.setDependencies( createReleaseDependencies( originalVersions, mappedVersions, releaseProject ) );
// rewrite plugins
releaseModel.getBuild().setPlugins( createReleasePlugins( originalVersions, mappedVersions, releaseProject ) );
// rewrite reports
releaseModel.getReporting().setPlugins( createReleaseReportPlugins( originalVersions, mappedVersions, releaseProject ) );
// rewrite extensions
releaseModel.getBuild().setExtensions( createReleaseExtensions( originalVersions, mappedVersions, releaseProject ) );
// rewrite profile dependencies here ...
// ...iterate over profiles and rewrite dependencies...
pathTranslator.unalignFromBaseDirectory( releaseProject.getModel(), project.getFile().getParentFile() );
return releaseModel;
}
}
{code}
> Versions defined in profiles are not updated
> --------------------------------------------
>
> Key: MRELEASE-354
> URL: http://jira.codehaus.org/browse/MRELEASE-354
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-7
> Environment: Maven version: 2.0.9
> Java version: 1.6.0_06
> OS name: "windows 2000" version: "5.0" arch: "x86" Family: "windows"
> Reporter: Martin von Zweigbergk
>
> Versions defined in profiles (in either <dependencies> or <dependecyManagement>) should be updated, regardless of which profile are active.
--
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] Commented: (MRELEASE-354) Versions defined in profiles are
not updated
Posted by "Tchavdar Roussanov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158305#action_158305 ]
Tchavdar Roussanov commented on MRELEASE-354:
---------------------------------------------
As a work around we use <version>${project.version}</version> fro the dependencies defined inside profiles.
> Versions defined in profiles are not updated
> --------------------------------------------
>
> Key: MRELEASE-354
> URL: http://jira.codehaus.org/browse/MRELEASE-354
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-7
> Environment: Maven version: 2.0.9
> Java version: 1.6.0_06
> OS name: "windows 2000" version: "5.0" arch: "x86" Family: "windows"
> Reporter: Martin von Zweigbergk
>
> Versions defined in profiles (in either <dependencies> or <dependecyManagement>) should be updated, regardless of which profile are active.
--
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] Commented: (MRELEASE-354) Versions defined in profiles are
not updated
Posted by "Mathias Arens (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157684#action_157684 ]
Mathias Arens commented on MRELEASE-354:
----------------------------------------
I have exactly the same problem. My dependencies in a profile section are not updated as well.
In my example the 'example-artifact' dependency in the JBoss-4.2.3.GA profile has not been updated to the new 0.5-SNAPSHOT version:
...
<profile>
<id>JBoss-4.2.3.GA</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<dependencies>
<dependency>
<groupId>example.groupId</groupId>
<artifactId>example-artifact</artifactId>
<version>0.4-SNAPSHOT</version>
<type>ejb</type>
<exclusions>
<exclusion>
<groupId>asm</groupId>
<artifactId>asm</artifactId>
</exclusion>
....
I agree with Martin that all dependencies defined in profile sections should be updated no matter which profile is active at the moment.
> Versions defined in profiles are not updated
> --------------------------------------------
>
> Key: MRELEASE-354
> URL: http://jira.codehaus.org/browse/MRELEASE-354
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-7
> Environment: Maven version: 2.0.9
> Java version: 1.6.0_06
> OS name: "windows 2000" version: "5.0" arch: "x86" Family: "windows"
> Reporter: Martin von Zweigbergk
>
> Versions defined in profiles (in either <dependencies> or <dependecyManagement>) should be updated, regardless of which profile are active.
--
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-354) Versions defined in profiles are not
updated
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MRELEASE-354.
--------------------------------------
Resolution: Fixed
Fix Version/s: 2.3
Assignee: Benjamin Bentmann
Fixed in [r1179704|http://svn.apache.org/viewvc?view=revision&revision=1179704].
> Versions defined in profiles are not updated
> --------------------------------------------
>
> Key: MRELEASE-354
> URL: https://jira.codehaus.org/browse/MRELEASE-354
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-7
> Environment: Maven version: 2.0.9
> Java version: 1.6.0_06
> OS name: "windows 2000" version: "5.0" arch: "x86" Family: "windows"
> Reporter: Martin von Zweigbergk
> Assignee: Benjamin Bentmann
> Fix For: 2.3
>
>
> Versions defined in profiles (in either <dependencies> or <dependecyManagement>) should be updated, regardless of which profile are active.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-354) Versions defined in profiles are not
updated
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-354:
-------------------------------------
Component/s: prepare
> Versions defined in profiles are not updated
> --------------------------------------------
>
> Key: MRELEASE-354
> URL: http://jira.codehaus.org/browse/MRELEASE-354
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-7
> Environment: Maven version: 2.0.9
> Java version: 1.6.0_06
> OS name: "windows 2000" version: "5.0" arch: "x86" Family: "windows"
> Reporter: Martin von Zweigbergk
>
> Versions defined in profiles (in either <dependencies> or <dependecyManagement>) should be updated, regardless of which profile are active.
--
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] (MRELEASE-354) Versions defined in profiles are not updated
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly updated MRELEASE-354:
--------------------------------------
Fix Version/s: (was: 2.3)
2.2.2
> Versions defined in profiles are not updated
> --------------------------------------------
>
> Key: MRELEASE-354
> URL: https://jira.codehaus.org/browse/MRELEASE-354
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-7
> Environment: Maven version: 2.0.9
> Java version: 1.6.0_06
> OS name: "windows 2000" version: "5.0" arch: "x86" Family: "windows"
> Reporter: Martin von Zweigbergk
> Assignee: Benjamin Bentmann
> Fix For: 2.2.2
>
>
> Versions defined in profiles (in either <dependencies> or <dependecyManagement>) should be updated, regardless of which profile are active.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MRELEASE-354) Versions defined in
profiles are not updated
Posted by "Mathias Arens (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157684#action_157684 ]
Mathias Arens edited comment on MRELEASE-354 at 12/11/08 4:10 AM:
------------------------------------------------------------------
I have exactly the same problem. My dependencies in a profile section are not updated as well.
In my example the 'example-artifact' dependency in the JBoss-4.2.3.GA profile has not been updated to the new 0.5-SNAPSHOT version:
{code:xml}
...
<profile>
<id>JBoss-4.2.3.GA</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<dependencies>
<dependency>
<groupId>example.groupId</groupId>
<artifactId>example-artifact</artifactId>
<version>0.4-SNAPSHOT</version>
<type>ejb</type>
<exclusions>
<exclusion>
<groupId>asm</groupId>
<artifactId>asm</artifactId>
</exclusion>
....
{code}
I agree with Martin that all dependencies defined in profile sections should be updated no matter which profile is active at the moment.
was (Author: mathiasarens):
I have exactly the same problem. My dependencies in a profile section are not updated as well.
In my example the 'example-artifact' dependency in the JBoss-4.2.3.GA profile has not been updated to the new 0.5-SNAPSHOT version:
...
<profile>
<id>JBoss-4.2.3.GA</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<dependencies>
<dependency>
<groupId>example.groupId</groupId>
<artifactId>example-artifact</artifactId>
<version>0.4-SNAPSHOT</version>
<type>ejb</type>
<exclusions>
<exclusion>
<groupId>asm</groupId>
<artifactId>asm</artifactId>
</exclusion>
....
I agree with Martin that all dependencies defined in profile sections should be updated no matter which profile is active at the moment.
> Versions defined in profiles are not updated
> --------------------------------------------
>
> Key: MRELEASE-354
> URL: http://jira.codehaus.org/browse/MRELEASE-354
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-7
> Environment: Maven version: 2.0.9
> Java version: 1.6.0_06
> OS name: "windows 2000" version: "5.0" arch: "x86" Family: "windows"
> Reporter: Martin von Zweigbergk
>
> Versions defined in profiles (in either <dependencies> or <dependecyManagement>) should be updated, regardless of which profile are active.
--
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