On 8/22/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
That's what i was suggesting.
Forking the plugin to make it usable *now* on G 1.1.
I will begin the backport now.
I don' think this will really help anything right now...
Even if the plugin version is a non-snapshot... all of the
dependencies it has on G are all 1.2-SNAPSHOT, which is not going to
change for sometime as we work towards the 1.2 release.
Having the plugin in two places is just going to cause them to become
out of sync.
If you really want to use a m2 plugin for G 1.1, then I suggest
someone port the m2 plugin to use G 1.1 artifacts and then add the
plugin module to the 1.1 branch... make it work and then be done with
it.
That's what i was suggesting.
Forking the plugin to make it usable *now* on G 1.1.
I will begin the backport now.
--jason
On Aug 22, 2006, at 8:06 AM, Guillaume Nodet wrote:
> The car-maven-plugin is used as part of the geronimo build in G 1.2.
> This plugin is also very usefull to build Geronimo plugins targeted
> to G 1.1,
> but has recently changed in a *slight* incompatible way.
>
> However, I think that:
> * it may be difficult in the future to ensure that a single maven
> plugin
> will be able to create car files for all past and future
> version of Geronimo
> * G 1.1 is out and a minor release is about to go. I think that
> it will benefit
> users to be able to write Geronimo 1.1 plugins wihtout
> relying on a
> snapshot plugin.
>
> Hence, I propose that the plugin be forked to a new location,
> /devtools/maven-plugin/geronimo-1.x/car-maven-plugin
> (any better idea ?)
> and that we release this plugin at the same time that the 1.1.1 is
> out.
>
> Thoughts ?
>
> --
> Cheers,
> Guillaume Nodet
--
Cheers,
Guillaume Nodet
