On 06/09/2007, at 4:21 AM, Jason van Zyl wrote:
On 4 Sep 07, at 10:50 PM 4 Sep 07, Jason van Zyl wrote:
Hi,
I would like to make a single module for plugin execution and this
is the first step. The motivator is being able to isolate a
version of a plugin apis runtime. These modules do not vary
independently in practice and they are not useful separately. I
really would like people to look at the top-level source tree and
easily see the key moving parts.
Any objections?
Doesn't seem to be, I'm going to merge these now.
Sorry, only just got around to this mail.
This will introduce a dependency on the plexus container and maven-
artifact for every single plugin - is that really desirable?
Currently, the plugins can depend on the API without needing the
plugin descriptor (which is basically used by tooling and the maven
internals). Seems best separated to me.
Cheers,
Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
