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
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
On 5 Sep 07, at 3:43 PM 5 Sep 07, Brett Porter wrote:
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
On 5 Sep 07, at 3:43 PM 5 Sep 07, Brett Porter wrote:
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
On 06/09/2007, at 9:18 AM, Jason van Zyl wrote:
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?
No it won't
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
