On 7 Sep 07, at 1:58 PM 7 Sep 07, [EMAIL PROTECTED] wrote:
Author: jdcasey
Date: Fri Sep 7 13:58:21 2007
New Revision: 573699
URL: http://svn.apache.org/viewvc?rev=573699view=rev
Log:
Fixing core-it-plugins so they won't bomb on surefire:test with NPE
if there is nothing under
-Original Message-
From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
Sent: vendredi 11 août 2006 13:05
To: Maven Developers List
Subject: Re: Integration testing plugins
Vincent Massol wrote:
Also, Kenney do you know if the it plugin can now be used to test a
plugin
Actually, pointing at a different local repo for the purposes of a build is
trivial. However, in the case of testing a plugin, you have to install the
plugin somewhere, then run a build that uses that plugin...this is not the
case with anything other than Maven components, which makes it an
-Original Message-
From: Kenney Westerhof [mailto:[EMAIL PROTECTED]
Sent: vendredi 11 août 2006 00:13
To: Maven Developers List
Subject: Re: Integration testing plugins
Hi John,
It seems that the maven-invoker-plugin does actually the same thing
as the maven-it-plugin
Vincent Massol wrote:
Also, Kenney do you know if the it plugin can now be used to test a plugin
that is being built for the first time? I remember that I didn't activate it
on the clover plugin because it would work only if the clover plugin was
installed in the local repository and this
This should be solved by the stage/unstage mojos in the plugin-test plugin.
That's its only current purpose. It will stage a new plugin artifact into
the local repository, backing up what was there before, then clear the
pluginManager's cache of that plugin, in case it's been resolved already.
On 11 Aug 06, at 9:18 AM 11 Aug 06, John Casey wrote:
This should be solved by the stage/unstage mojos in the plugin-test
plugin.
That's its only current purpose. It will stage a new plugin
artifact into
the local repository, backing up what was there before, then clear the
pluginManager's
it doesn't backup the whole local repository, only the files that will be
affected by a plugin install. It should be relatively stable in terms of the
backup/restore data transfer size...varying only by the number of
repositories that were consulted for that artifact (because there is a set
of
On 11 Aug 06, at 11:25 AM 11 Aug 06, John Casey wrote:
it doesn't backup the whole local repository, only the files that
will be
affected by a plugin install. It should be relatively stable in
terms of the
backup/restore data transfer size...varying only by the number of
repositories that
Hi,
I wanted to let people know about something I've been working on for the
assembly plugin. As anyone watching the commit notifications has probably
noticed, I've recently completed a large refactor of the assembly plugin,
with the aim of making it more modular and easier to unit test. While
Hi John,
It seems that the maven-invoker-plugin does actually the same thing
as the maven-it-plugin (still in the sandbox), except you added some
prebuild and verification steps.
Maybe we can merge them somehow, or delete the maven-it-plugin (which I
actually wrote in the pre-embedder era
cool. Can we get this written up in the wiki/docs like Jesse's stuff was?
How about starting the plugin developers centre on the website? :)
- Brett
On 11/08/2006 8:06 AM, John Casey wrote:
Hi,
I wanted to let people know about something I've been working on for the
assembly plugin. As
Yeah, I will follow up this thread with wiki documentation. I'd like to
approach it as more of a testing maven components with a special section
on plugins, personally...because I think a lot of the principles will apply
in both cases. WDYT?
Kenney: yeah, I actually revamped/gutted the it plugin
On Tue, 2006-01-31 at 05:26 -0600, Allison, Bob wrote:
I also see a need for being able to inject mock objects of Plexus
components (the RPM plugin uses a Plexus Archiver). The unit test will
need to construct these mock objects and set their expectations before
they are injected into the
Developers List
Subject: unit testing vs integration testing plugins
Hi,
I wanted to get some feedback from other devs on this topic.
Historically, I think we've done very little of both and would like to
change that. But most of the tests cropping up seem to be integration
tests, because
:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: mardi 31 janvier 2006 01:57
To: Maven Developers List
Subject: Re: unit testing vs integration testing plugins
We probably need to provide some plugin test infrastructure like mock
objects and utilities to do the common test tasks.
On 1/30
Brett Porter wrote:
Hi,
I wanted to get some feedback from other devs on this topic.
Historically, I think we've done very little of both and would like to
change that. But most of the tests cropping up seem to be integration
tests, because they are probably an easier mechanism than to setup
Hi,
I wanted to get some feedback from other devs on this topic.
Historically, I think we've done very little of both and would like to
change that. But most of the tests cropping up seem to be integration
tests, because they are probably an easier mechanism than to setup the
preconditions of the
I have always kinda figured the rule of thumb regarding tests and artifacts
is unit tests would test anything inside of the artifact and integration
tests would encompass extra-artifact scope testing
and I totally agree, I think unit testing within mojo projects would be a
lot more prelavent with
We probably need to provide some plugin test infrastructure like mock
objects and utilities to do the common test tasks.
On 1/30/06, Brett Porter [EMAIL PROTECTED] wrote:
Hi,
I wanted to get some feedback from other devs on this topic.
Historically, I think we've done very little of both and
It might be nice to have a harness which would allow unit testing
plugins. The only problem is you have to test the test harness...this is
a problem we've run into time and again with all of the test harnesses
we have for Maven. I've personally fixed failures based on assumptions
in the
21 matches
Mail list logo
