I agree with Arnaud. If they had a shared release cycle it would make sense to
group together the release manager with the plugin. But since all three parts
are released separately, I think it would be better to move the plugin part to
plugins and the manager to shared.
Arnaud HERITIER wrote:
Why didn't we store the maven-release-manager under shared and the plugin
under plugins ? Just to share the version used of SCM ?
Arnaud
On Mon, Nov 24, 2008 at 6:08 PM, Arnaud HERITIER <[EMAIL PROTECTED]>wrote:
Hi
Is it normal to have 3 lifecycles for the release plugin ?
- The release plugin itself : 2.0-beta-9-SNAPSHOT in the trunk
- The release library : 1.0-alpha-6-SNAPSHOT in the trunk
- The release pom parent : 6-SNAPSHOT in the trunk
But we have only one Jira : https://jira.codehaus.org/browse/MRELEASE
Is it just to show that we can handle various versions in a release or is
there a real need to have a separate lifecycle ?
Cheers,
--
..........................................................
Arnaud HERITIER
12 guidelines to boost your productivity with a Java software factory -
http://tinyurl.com/56s9tw
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
