Ok. I keep the plugin and the manager together but I use everywhere the
version of the plugin.
Arnaud
On Tue, Nov 25, 2008 at 12:42 AM, Jason van Zyl <[EMAIL PROTECTED]>wrote:
> On 24-Nov-08, at 1:04 PM, Arnaud HERITIER wrote:
>
> Why didn't we store the maven-release-manager under shared and t
On 24-Nov-08, at 1:04 PM, 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 ?
Because they always got released together because they are so coupled.
When you fix something in the plugin yo
I'm not quite sure why the versions are different, I'd go more towards
having one release cycle.
- Brett
On 25/11/2008, at 9:06 AM, Paul Gier wrote:
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 sin
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 rele
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
