There's a few things going on here:
- the plugin report uses the plugin tools, which really shouldn't be in
the Maven release cycle since they are really independant (but they are
there to make bootstrap possible without the shared SVN repo)
- the plugin descriptor generator uses the model that is in the Maven
release. This is really quite unfortunate.
The first one could be eased by not referencing the new fields in the
tools until after the next release when we can take a prereq bump. This
would make the plugin plugin able to use 2.0.5-SNAPSHOT of the tools,
while still only having the maven 2.0 prereq from maven-plugin-descriptor.
The second one really should be fixed as you want to target a particular
Maven version for a plugin, not target the running version of Maven. For
this, we probably need to get the model out of the Maven core in some
way, or switch to constructing the descriptor as XML, not using the model.
For right now, everything works, but to use the next release of the
plugin plugin, you need the next release of Maven (however, the previous
version will of course continue to work and could be branched). That is,
those living on the edge just need to step a little closer. Those
watching from a distance are not at risk.
I'm not sure any of that made sense :)
- Brett
On 13/07/2006 7:54 PM, Trygve Laugstøl wrote:
Dennis Lundberg wrote:
Brett Porter wrote:
This shouldn't have broken - needs investigation.
A while back, we agreed to add a feature to 2.0.5 (the implementation
attribute).
The plugin plugin was updated to use the new tools and such. However,
it also has a prereq of maven 2.0.5, so maven 2.0.4 and below which
give this error should use the previous version of the plugin.
Are you saying that I need to use Maven 2.0.5 SNAPSHOT to build all
plugins from now on?
I prefer to stay on the released version of Maven as long as possible,
to make sure that I have the same environment as most users do. But I
see the chicken-and-egg problem here.
If the plugin plugin has a prereq on Maven 2.0.5 shouldn't it give
some sort of understandable error message to the user if he/she tries
to run it with Maven 2.0.4, instead of just a stack trace?
What about using profiles for this?
I wonder if we should add the building of the plugins using the
different releases of Maven to make sure that they keep the backwards
compatability (Sorry, I do not have time to fix it :( ).
--
Trygve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
