You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Marcus Linke (JIRA)" <ji...@codehaus.org> on 2010/10/04 14:22:32 UTC
[jira] Created: (MRELEASE-603) Allow configuration of goals to be
executed after release creation
Allow configuration of goals to be executed after release creation
------------------------------------------------------------------
Key: MRELEASE-603
URL: http://jira.codehaus.org/browse/MRELEASE-603
Project: Maven 2.x Release Plugin
Issue Type: New Feature
Affects Versions: 2.1
Reporter: Marcus Linke
Priority: Minor
It would be nice if the release plugin allows the configuration of some goals to be executed after the release creation. This could be used for example to configure the automatic execution of the maven-versions-plugin to update the dependencies versions of the newly created snaphot.
--
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-603) Allow configuration of goals to be executed
after release creation
Posted by "Marcus Linke (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298728#comment-298728 ]
Marcus Linke commented on MRELEASE-603:
---------------------------------------
{quote}
Now we want to release earB-2, which probably depends on shared-2-SNAPSHOT (not the latest snapshot) since earB-1 was released before shared-2.
You probably want this release to use shared-3.
{quote}
This is exactly the problem. We don't want the release of earB-2 use shared-3 but shared-2 as the CI builds for earB depends on shared-2-SNAPSHOT at this time and we can't guarantee that shared-3 is compatible with shared-2-SNAPSHOT anymore.
After the release of earB the new earB-3-SNAPSHOT should depend on shared-4-SNAPSHOT so the CI system will show us incompatibilities with the new shared component and developers are invited to fix this. All this could be achived by hooking in {{versions-maven-plugin:use-latest-version}} into the (post-)release process. The {{versions-maven-plugin:use-latest-version}} goal is highly configurable and would allow us to exclude and include specific artifacts per project.
The checkin to SCM could be done manually by the release maintainer but could be configured via the new post-perform goals option too.
> Allow configuration of goals to be executed after release creation
> ------------------------------------------------------------------
>
> Key: MRELEASE-603
> URL: https://jira.codehaus.org/browse/MRELEASE-603
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: Marcus Linke
> Assignee: Robert Scholte
> Priority: Minor
>
> It would be nice if the release plugin allows the configuration of some goals to be executed after the release creation. This could be used for example to configure the automatic execution of the maven-versions-plugin to update the dependencies versions of the newly created snaphot.
--
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] (MRELEASE-603) Allow configuration of goals to be executed
after release creation
Posted by "Marcus Linke (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Linke reopened MRELEASE-603:
-----------------------------------
To be more clear i would like to have something like a 'postPerformGoals' configuration option. These configured goals should be run AFTER the whole release process is performed. It would be great because i want to run the 'versions-maven-plugin' on the newly created SNAPSHOT version as part of the release process. Maybe there is another way to implement this?
> Allow configuration of goals to be executed after release creation
> ------------------------------------------------------------------
>
> Key: MRELEASE-603
> URL: https://jira.codehaus.org/browse/MRELEASE-603
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: Marcus Linke
> Assignee: Robert Scholte
> Priority: Minor
>
> It would be nice if the release plugin allows the configuration of some goals to be executed after the release creation. This could be used for example to configure the automatic execution of the maven-versions-plugin to update the dependencies versions of the newly created snaphot.
--
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] (MRELEASE-603) Allow configuration of goals to be executed
after release creation
Posted by "Marcus Linke (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298209#comment-298209 ]
Marcus Linke commented on MRELEASE-603:
---------------------------------------
This is our scenario here: We have a strongly modularized project with two resulting deployment units (EARs) for our two different national branches. There are a couple of base projects that both EARs depends on. The problem is, that development is usually done by focusing on only one of the deployment units and we can't release both EARs in parallel. So the consequence is that the non-released EAR depends on older SNAPSHOTs which is OK but only until releasing it. The 'versions-maven-plugin's 'use-latest-snapshots' goal (http://mojo.codehaus.org/versions-maven-plugin/use-latest-snapshots-mojo.html) should be executed as part of the release process to guarantee that the new SNAPSHOT version depends on latest base project SNAPSHOT's itself.
> Allow configuration of goals to be executed after release creation
> ------------------------------------------------------------------
>
> Key: MRELEASE-603
> URL: https://jira.codehaus.org/browse/MRELEASE-603
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: Marcus Linke
> Assignee: Robert Scholte
> Priority: Minor
>
> It would be nice if the release plugin allows the configuration of some goals to be executed after the release creation. This could be used for example to configure the automatic execution of the maven-versions-plugin to update the dependencies versions of the newly created snaphot.
--
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] (MRELEASE-603) Allow configuration of goals to be executed
after release creation
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298685#comment-298685 ]
Robert Scholte commented on MRELEASE-603:
-----------------------------------------
The {{perform}}-goal is about checking out the project by the release-tag and run several release-goals on that projects, usualy {{deploy}} and {{deploy-site}}.
Your goal is to have the pom.xml ready for the next development-cycle, which should be part of the {{prepare}}-goal.
I think that a post-perform goal wouldn't help.
Correct me if I'm wrong, but this is how I read your story:
In this order the projects have been released:
* shared-1
* earA-1 (using shared-1)
* earB-1 (using shared-1)
* shared-2
* earA-2 (using shared-2)
* earA-3 (using shared-2)
* shared-3
Now we want to release earB-2, which probably depends on shared-2-SNAPSHOT (not the latest snapshot) since earB-1 was released before shared-2.
You probably want this release to use shared-3.
So it seems like you've developed with the wrong snapshot version, and no post-goal would have helped here.
I'd prefer not to use a fully automated call of {{use-latest-version}}, but that's something a CI-system could do for you. Also think of the checkin, which has to follow.
> Allow configuration of goals to be executed after release creation
> ------------------------------------------------------------------
>
> Key: MRELEASE-603
> URL: https://jira.codehaus.org/browse/MRELEASE-603
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: Marcus Linke
> Assignee: Robert Scholte
> Priority: Minor
>
> It would be nice if the release plugin allows the configuration of some goals to be executed after the release creation. This could be used for example to configure the automatic execution of the maven-versions-plugin to update the dependencies versions of the newly created snaphot.
--
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] (MRELEASE-603) Allow configuration of goals to be executed
after release creation
Posted by "Marcus Linke (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Linke closed MRELEASE-603.
---------------------------------
Resolution: Duplicate
Fix Version/s: 2.2
> Allow configuration of goals to be executed after release creation
> ------------------------------------------------------------------
>
> Key: MRELEASE-603
> URL: https://jira.codehaus.org/browse/MRELEASE-603
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: Marcus Linke
> Assignee: Robert Scholte
> Priority: Minor
> Fix For: 2.2
>
>
> It would be nice if the release plugin allows the configuration of some goals to be executed after the release creation. This could be used for example to configure the automatic execution of the maven-versions-plugin to update the dependencies versions of the newly created snaphot.
--
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] (MRELEASE-603) Allow configuration of goals to be executed
after release creation
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298811#comment-298811 ]
Robert Scholte commented on MRELEASE-603:
-----------------------------------------
So the story is clear. But I'm just wondering what is wrong with the [completionGoals|http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#completionGoals] during {{release:prepare}}? If I'm correct this was exactly why Stephen added MRELEASE-621.
I can't think of a reason why you want to wait untill the project is checked out by tag and deployed. ( And you'll get the checkin for free during the prepare :) )
> Allow configuration of goals to be executed after release creation
> ------------------------------------------------------------------
>
> Key: MRELEASE-603
> URL: https://jira.codehaus.org/browse/MRELEASE-603
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: Marcus Linke
> Assignee: Robert Scholte
> Priority: Minor
>
> It would be nice if the release plugin allows the configuration of some goals to be executed after the release creation. This could be used for example to configure the automatic execution of the maven-versions-plugin to update the dependencies versions of the newly created snaphot.
--
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] (MRELEASE-603) Allow configuration of goals to be executed
after release creation
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297898#comment-297898 ]
Robert Scholte commented on MRELEASE-603:
-----------------------------------------
Although it's nice you're already thinking in solutions, I'd like to focus on the problem first. Why do you want to run the {{versions-maven-plugin}} (and which goal(s))? Is this something which could already be solved during the {{release:prepare}}?
> Allow configuration of goals to be executed after release creation
> ------------------------------------------------------------------
>
> Key: MRELEASE-603
> URL: https://jira.codehaus.org/browse/MRELEASE-603
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: Marcus Linke
> Assignee: Robert Scholte
> Priority: Minor
>
> It would be nice if the release plugin allows the configuration of some goals to be executed after the release creation. This could be used for example to configure the automatic execution of the maven-versions-plugin to update the dependencies versions of the newly created snaphot.
--
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] (MRELEASE-603) Allow configuration of goals to be executed
after release creation
Posted by "Marcus Linke (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298859#comment-298859 ]
Marcus Linke commented on MRELEASE-603:
---------------------------------------
OK, so it seems i've totally misunderstood the meaning of that {{completionGoals}} option. Thanks for being so patient with me! I will close this issue now.
> Allow configuration of goals to be executed after release creation
> ------------------------------------------------------------------
>
> Key: MRELEASE-603
> URL: https://jira.codehaus.org/browse/MRELEASE-603
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: Marcus Linke
> Assignee: Robert Scholte
> Priority: Minor
> Fix For: 2.2
>
>
> It would be nice if the release plugin allows the configuration of some goals to be executed after the release creation. This could be used for example to configure the automatic execution of the maven-versions-plugin to update the dependencies versions of the newly created snaphot.
--
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] (MRELEASE-603) Allow configuration of goals to be executed
after release creation
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-603.
-----------------------------------
Resolution: Duplicate
Assignee: Robert Scholte
> Allow configuration of goals to be executed after release creation
> ------------------------------------------------------------------
>
> Key: MRELEASE-603
> URL: https://jira.codehaus.org/browse/MRELEASE-603
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: Marcus Linke
> Assignee: Robert Scholte
> Priority: Minor
>
> It would be nice if the release plugin allows the configuration of some goals to be executed after the release creation. This could be used for example to configure the automatic execution of the maven-versions-plugin to update the dependencies versions of the newly created snaphot.
--
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