On 9/18/06, Brett Porter <[EMAIL PROTECTED]> wrote:
On 18/09/06, jerome lacoste <[EMAIL PROTECTED]> wrote:
> I completely agree. In fact building plugins now requires maven 2.0.5
> and this made me put a pause on working on mojo plugins: I want to use
> a stable build with known shortcomings, and not depend on a moving
> development platform.
This isn't true.
If you build all the plugins from trunk, then yes, 2.0.5 is required,
as the plugin plugin has adopted some new features. It's likely to be
reverted to avoid the headaches, but it is a separate issue. It was
exacerbated by that version being set to the default for all maven
plugins. That is being rolled back in many places already and is a
simple parent version change.
However, you can keep using the released version of the plugin plugin
to build your plugins by sticking to non snapshot repositories.
Thanks for pointing that out. I though that the mojo and maven plugins
build issues had the same root (i.e. caused because of a change in the
root pom). I now realize the problem in the mojo build was caused by
one of my plugins requiring a SNAPSHOT version of the
maven-jar-plugin, which has been released when I was away. So nothing
to do with the root pom.
Thanks Brett,
Jerome
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
