This is done. The plugin-tools trunk relies on maven-2.0.5, while
there is a branch that requires maven-2.0.4 and removes the
implementation/since attributes. The plugin-plugin trunk relies on
the latter branch so works with 2.0.4. I'll be calling a release on
that in the near future.
Che
On 15/09/2006, at 5:09 AM, Jason van Zyl wrote:
Are we just moving it, though it will still be coupled to the core?
If the dependency is in one direction so the core depends on the
plugin api that's cool with me.D
I was thinking the plugin-api would stay in Maven (and plugin-
descript
On 12 Sep 06, at 4:18 AM 12 Sep 06, Brett Porter wrote:
Hi,
I'd like to propose moving the plugin-tools and reporting-impl to
shared, to decouple plugin releases from the maven core releases.
Right now, building the plugins is blocked around maven 2.0.5.
The one downside to this is that
An user answer woukld be :
release a 2.0.5 version to publicise the bubfixes :)
Raphaël
2006/9/12, Brett Porter <[EMAIL PROTECTED]>:
Hi,
I'd like to propose moving the plugin-tools and reporting-impl to
shared, to decouple plugin releases from the maven core releases.
Right now, building the
Hi,
I'd like to propose moving the plugin-tools and reporting-impl to
shared, to decouple plugin releases from the maven core releases.
Right now, building the plugins is blocked around maven 2.0.5.
The one downside to this is that the bootstrap requires the plugin
tools to build plugins
