You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Brett Porter <br...@apache.org> on 2006/09/12 04:18:27 UTC
[discuss] move the plugin tools and reporting to shared
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 for the first time, so we'd need to find an
alternate solution to that. It already depends on binaries of maven-
archiver, so I'd suggest we take binaries of these too. I'd move
pluggy to the bootstrap instead of to shared.
We still have on the bootstrap's roadmap to be able to build
completely from source which is a separate issue.
The other alternative to this is to start thinking about cutting a
2.0.5 release with what we have now.
WDYT?
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [discuss] move the plugin tools and reporting to shared
Posted by Brett Porter <br...@apache.org>.
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-
descriptor model), but the plugin tools - the stuff used by the
plugin plugin - be moved.
The core doesn't depend on them - just the bootstrap.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [discuss] move the plugin tools and reporting to shared
Posted by Jason van Zyl <ja...@maven.org>.
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 the bootstrap requires the plugin
> tools to build plugins for the first time, so we'd need to find an
> alternate solution to that. It already depends on binaries of maven-
> archiver, so I'd suggest we take binaries of these too. I'd move
> pluggy to the bootstrap instead of to shared.
>
> We still have on the bootstrap's roadmap to be able to build
> completely from source which is a separate issue.
>
> The other alternative to this is to start thinking about cutting a
> 2.0.5 release with what we have now.
>
> WDYT?
>
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
> - Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Jason van Zyl
jason@maven.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [discuss] move the plugin tools and reporting to shared
Posted by Raphaël Piéroni <ra...@gmail.com>.
An user answer woukld be :
release a 2.0.5 version to publicise the bubfixes :)
Raphaël
2006/9/12, Brett Porter <br...@apache.org>:
>
> 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 for the first time, so we'd need to find an
> alternate solution to that. It already depends on binaries of maven-
> archiver, so I'd suggest we take binaries of these too. I'd move
> pluggy to the bootstrap instead of to shared.
>
> We still have on the bootstrap's roadmap to be able to build
> completely from source which is a separate issue.
>
> The other alternative to this is to start thinking about cutting a
> 2.0.5 release with what we have now.
>
> WDYT?
>
> - Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>