I'm personally not very interested in merging the plugins. I can
explain more when I'm back from Thailand :-)
--jason
On Dec 18, 2007, at 3:13 PM, Jason van Zyl wrote:
On 17 Dec 07, at 12:17 AM 17 Dec 07, olivier lamy wrote:
Hi,
Agree on merge but in a new plugin or merging in maven-invoker-
plugin ?
Before starting this work, I'd like to release the current
maven-invoker-plugin to not delay some other releases which depends
on this.
I will call a vote today.
After we can work on the merge.
Thoughs ? or objections ?
You may actually want to approach the people who actually wrote
these plugins. They wrote them for a particular reason, so make sure
you talk to them before merging their code. The onus is on you to
make sure you've communicated with the respective authors.
--
Olivier
2007/12/17, nicolas de loof <[EMAIL PROTECTED]>:
I just looked at invoker plugin as part of maven-jar-plugin it
tests.
Looks very similar to shitty, just two diffs :
- shitty handles installing a test jar in the local repo. Invoker
requires
more conf in POM to install the jar in a custom local repo (the
way it is
used in MJAR)
- shitty uses groovy for verify scripts, verifier uses beanshell.
Both accept standard Java.
Couldn't those two plugins merge ? They are so similar !
2007/12/14, nicolas de loof <[EMAIL PROTECTED]>:
Not sure to understand, maybe I miss-used testing-harness :
I set a test POM with just the plugin configuration, so that I
can run :
File testPom = new File( getBasedir(),
"src/test/resources/compile.pom" );
Mojo mojo = (Mojo) lookupMojo( "compile", testPom );
assertNotNull( "Failed to configure the plugin", mojo );
mojo.execute();
Right, but then when my plugin has many plexus @component I have
to set
them in the test POM as configuration elements, using
implementation="XXXStub". So it seems this NOT to be a real maven
build.
The
EclipsePlugin requires a MavenProject with many sub-components,
that is
difficult to setup
Or maybe I missunderstood the use of this plugin ?
Nico.
2007/12/14, Brian E. Fox <[EMAIL PROTECTED]>:
AFAIK, shitty is similar to invoker, but does more : it install
the
current
artifact in local repo with version "testing" and invoke a maven
build.
Seems to be what the invoker it-test do. Shitty alos use groovy
scripts
to
test the result.
This is _exactly_ what the plugin testing harness (currently
used by
the
eclipse plugin) does.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
First, the taking in of scattered particulars under one Idea,
so that everyone understands what is being talked about ... Second,
the separation of the Idea into parts, by dividing it at the joints,
as nature directs, not breaking any limb in half as a bad carver
might.
-- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
