Rinku wrote:
One way could be to factor out the reusable bits out to a separate
Component. That should make plugins lightweight and allow components to
be used by more than just one Plugin.
This something that we always have been stressing. For the same reasons
it is important that plugins
Hi, Kenney,
On 7/11/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
This is not a maven mojo problem but a plugin design problem. Most
plugins, like the jar plugin and the surefire plugin, to name some,
are rather empty. The jar plugin just extracts information from the
MavenProject, giving it
Maven Developers List"
Sent: Tuesday, July 11, 2006 1:19 PM
Subject: Re: A plugins nature
There shouldn't be any reason you can't test as POJOs now (as long as
you add getters and setters). I was initially reluctant about the
extent of using the testing harness for testing - they
There shouldn't be any reason you can't test as POJOs now (as long as
you add getters and setters). I was initially reluctant about the extent
of using the testing harness for testing - they do seem more like
integration tests, but it has really been used as an assistant for
populating values (
This is not a maven mojo problem but a plugin design problem. Most
plugins, like the jar plugin and the surefire plugin, to name some,
are rather empty. The jar plugin just extracts information from the
MavenProject, giving it to maven-archiver (plexus-archiver under water),
and later updates the
On Tue, 11 Jul 2006, Carlos Sanchez wrote:
Indeed.
The mojo's should be as lightweight as possible - just the glue between
maven and the actual actions it performs.
This is not a maven mojo problem but a plugin design problem. Most
plugins, like the jar plugin and the surefire plugin, to name so
I think that's defenitely what we look for, pojos wrapped in mojos, or
at least mojos that can be used as pojos as much as possible
On 7/10/06, Mike Perham <[EMAIL PROTECTED]> wrote:
I would like to see plugins be made a little more independent from
Maven. You know how J2EE code is difficult to
I would like to see plugins be made a little more independent from
Maven. You know how J2EE code is difficult to test due to the need for
a container? Well, Maven is the container for plugins and that need for
a container makes it more difficult than necessary to test and reuse
plugins. There's
