The Apache Maven team is pleased to announce the release of the Apache
Maven Plugin Testing version, version 4.0.0-alpha-2
https://maven.apache.org/plugin-testing/
You can download the appropriate sources etc. from the download page:
https://maven.apache.org/plugin-testing/download.html
The Apache Maven team is pleased to announce the release of the
Maven Plugin Testing 4.0.0-alpha-1
https://maven.apache.org/plugin-testing
Release Notes - Maven Plugin Testing - Version 4.0.0-alpha-1
** Bug
* [MPLUGINTESTING-47] - Incorrect Mojo Java5 annotations in example
ov, wrote:
> Hello everyone.
>
> Maven-plugin maven-plugin-testing-harness
> <https://github.com/apache/maven-plugin-testing/tree/master/maven-plugin-testing-harness>
> still uses JUnit 4
> <https://github.com/apache/maven-plugin-testing/blob/7d6518b0d32d820efa15f7b4d022b852
Hello everyone.
Maven-plugin maven-plugin-testing-harness
<https://github.com/apache/maven-plugin-testing/tree/master/maven-plugin-testing-harness>
still uses JUnit 4
<https://github.com/apache/maven-plugin-testing/blob/7d6518b0d32d820efa15f7b4d022b8524a9b1d1b/maven-plugin-testin
jbossws project jaxws-tools-maven-plugin requires the updates in
maven-plugin-testing-harness-3.4.0-SNAPSHOT.
When is this version expected to go final
the user guide does discuss IDE integration :-)
-D
On Sun, Aug 30, 2020 at 5:19 PM Dan Tran wrote:
>
> I have been using takari-team for maven-plugin testing for Eclipse,
> however, the eclipse feature is currently stalled or not maintained.
>
> I wonder if the new framework wil
I have been using takari-team for maven-plugin testing for Eclipse,
however, the eclipse feature is currently stalled or not maintained.
I wonder if the new framework will work with m2e out of the box where I can
debug my plugin testing?
-D
Hi,
On 03/03/18 21:13, Martijn Verburg wrote:
Hi all,
So is the entirety of http://maven.apache.org/plugin-testing/maven-plugin-
testing-tools/ deprecated? We're building a maven plugin arpund detecting
split packages for Java9+ and have started down the testing-tools rabbit
hole..
Hi all,
So is the entirety of http://maven.apache.org/plugin-testing/maven-plugin-
testing-tools/ deprecated? We're building a maven plugin arpund detecting
split packages for Java9+ and have started down the testing-tools rabbit
hole...
Cheers,
Martijn
On 2 March 2018 at 07:17, Olivier
rg/plugin-testing/maven-plugin-testing-tools/ was
> the right tool, but its javadoc is completly deprecated and no
> replacement mentioned.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For
Hi.
I want to invoke a maven build as part of the unit test. I thought that
http://maven.apache.org/plugin-testing/maven-plugin-testing-tools/ was
the right tool, but its javadoc is completly deprecated and no
replacement mentioned
I recommend that you use invoker for testing plugins.
On 9 November 2017 at 13:07, Francois MAROT
wrote:
> I'm no expert at all, but just to let you know: last time I tried the test
> harness plugin, I also gave up... :(
> I think some advocate to use the maven-invoker-plugin to test in real
> c
I'm no expert at all, but just to let you know: last time I tried the test
harness plugin, I also gave up... :(
I think some advocate to use the maven-invoker-plugin to test in real
conditions with much less dependency problems. You can have a look there:
https://maven.apache.org/plugin-developers/
Hi all,
I’m trying to run simple test using maven-plugin-testing-harness (3.3.0). But
it looks like plugin doesn’t support maven 3 (3.2.2) ( it uses old plexus
container and doesn’t support new eclipse sisu).
java.lang.NoSuchMethodError:
org.codehaus.plexus.DefaultPlexusContainer.(Lorg
maven-invoker-plugin looks very useful, but it just adds to the frustration
that the maven website guided me down this path with
maven-plugin-testing-harness without a single mention of
maven-invoker-plugin.
you might want to put a link in there in the "my first mojo resources"
section.
Hi
IMHO using the maven invoker plugin is a better way as you can easily test
your plugin with different core versions.
but it's only my POV :-)
On 23 August 2017 at 18:03, ahardy42 wrote:
> After a concentrated stint of experimentation, I have setup my tests using
> the maven-plu
After a concentrated stint of experimentation, I have setup my tests using
the maven-plugin-testing-harness so that the tests run with a live remote
repository and have all the resources provided in the target/test-classes
directory.
The solution is here:
https://stackoverflow.com/questions
On 26/07/17 20:13, Karl Heinz Marbaise wrote:
>> and the link to git repo is 404
>
> https://github.com/apache/maven-plugin-testing
>
> but it's out of date correct...
>
> I have created an appropriate INFRA ticket to fix this[1].
>
>
> [1]: https://iss
On 26/07/17 11:49, ahardy42 wrote:
> Is there life is in this testing harness still?
>
> I'm looking at
> https://maven.apache.org/plugin-testing/maven-plugin-testing-harness/
Hi All,
while I've made a lot of progress with my plugin testing with the
maven-plugin-testing-ha
Hi,
On 26/07/17 20:13, Karl Heinz Marbaise wrote:
Hi,
On 26/07/17 11:49, ahardy42 wrote:
Is there life is in this testing harness still?
I'm looking at
https://maven.apache.org/plugin-testing/maven-plugin-testing-harness/
The link to JIRA returns 503 -
http://jira.codehaus.org/b
Hi,
On 26/07/17 11:49, ahardy42 wrote:
Is there life is in this testing harness still?
I'm looking at
https://maven.apache.org/plugin-testing/maven-plugin-testing-harness/
The link to JIRA returns 503 -
http://jira.codehaus.org/browse/MPLUGINTESTING
Outch that are the old links
Is there life is in this testing harness still?
I'm looking at
https://maven.apache.org/plugin-testing/maven-plugin-testing-harness/
The link to JIRA returns 503 -
http://jira.codehaus.org/browse/MPLUGINTESTING
and the link to git repo is 404
I can imagine there is a big population of
Hi All
I'm writing a mojo and using maven-plugin-testing-harness.
Is there an issue with Java 8 streams or lambdas? When I include a method
on my mojo with some lambda functionality, I get this exception when it
tries to generate the mojo:
[ERROR] Failed to execute
.com/takari/takari-plugin-testing-project
Thanks for the assistance.
Looks like I'll be switching to Takari today.
M
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
You are missing the dependencies which contain the necessary classes. I made a
PR for you. The project test now executes.
FYI, I use this all the time now for plugin unit and integration testing:
https://github.com/takari/takari-plugin-testing-project
> On Nov 13, 2015, at 5:30 PM,
>
On 2015-11-13T17:09:36 -0500
Jason van Zyl wrote:
> You must be running with a version of Maven where that class does not exist?
> That error means you’re using a library where that class was present during
> building but not present at runtime. You running something older than Maven
> 2.2.x?
You must be running with a version of Maven where that class does not exist?
That error means you’re using a library where that class was present during
building but not present at runtime. You running something older than Maven
2.2.x?
> On Nov 13, 2015, at 4:59 PM, org.apache.maven.u...@io7m.c
On 2015-11-13T21:07:23 +
wrote:
> On 2015-11-13T21:39:06 +0100
> Karl Heinz Marbaise wrote:
> >
> > Better use at least version 3.0 of this...
>
> I'll try 3.0.
No luck, unfortunately. Same error.
M
-
To unsubscribe, e-
'Lo!
On 2015-11-13T21:39:06 +0100
Karl Heinz Marbaise wrote:
>
> Why are you using this:
>
>
>org.apache.maven
>maven-plugin-api
>2.0
>
>
> Better use at least version 3.0 of this...
Because the documentation says 2.0:
https://maven.apache.org/guides/plugi
Hi,
On 11/13/15 2:23 PM, org.apache.maven.u...@io7m.com wrote:
On 2015-11-13T10:03:54 +
wrote:
Hello.
I'm attempting to add a Maven plugin to a small compiler project:
Here's a tiny repro case.
https://github.com/io7m/mvn-bug-20151113
Why are you using this:
org.apache.mav
On 2015-11-13T10:03:54 +
wrote:
> Hello.
>
> I'm attempting to add a Maven plugin to a small compiler project:
Here's a tiny repro case.
https://github.com/io7m/mvn-bug-20151113
M
-
To unsubscribe, e-mail: users-unsubscr
Hello.
I'm attempting to add a Maven plugin to a small compiler project:
https://github.com/io7m/jpra
However, given the following trivial pom.xml:
https://github.com/io7m/jpra/blob/develop/io7m-jpra-maven-plugin/pom.xml
... and the following no-op unit test:
https://github.com/io7m/jp
The Apache Maven team is pleased to announce the release of the Apache
Maven Plugin Testing, version 3.1.0
The Maven Plugin Testing contains the necessary tools to be able
to test Maven Plugins.
http://maven.apache.org/plugin-testing/
You should specify the version in your project's depen
Check out eg. the source of the Android Maven Plugin on how you can hook
this all up.
> Hi All,
>
>
> Can anyone actually provide a link to a working example of the plugin
> testing framework?
>
>
> Iâm using maven 3.0.5, and have even tried compiling the snapshot
&
> Hi All,
>
>
> Can anyone actually provide a link to a working example of the plugin
> testing framework?
>
>
> I’m using maven 3.0.5, and have even tried compiling the snapshot
> 2.2-SNAPSHOT version of maven-plugin-testing-harness, but still receive
> errors about n
our le contenu fourni.
> Date: Tue, 12 Mar 2013 15:45:00 -0700
> From: mikes...@gmail.com
> To: users@maven.apache.org
> Subject: Plugin Testing?
>
> Hi All,
>
>
> Can anyone actually provide a link to a working example of the plugin testing
> framework?
>
Hi All,
Can anyone actually provide a link to a working example of the plugin testing
framework?
I’m using maven 3.0.5, and have even tried compiling the snapshot 2.2-SNAPSHOT
version of maven-plugin-testing-harness, but still receive errors about not
being able to find the component in my
The Maven team is pleased to announce the release of the Maven Plugin
Testing, version 1.3 and 2.1
This release is Java7 compatible and updates all the dependencies of
plugin-testing,
especially easymock to version 2.5.2. Projects wishing to upgrade to
this version
will need to update their own
juin 2012 10:29:05 Benjamin Reed a écrit :
> I'm trying to write a maven plugin. I've added
> maven-plugin-testing-harness to my project as a test dependency, and
> created a very simple test that right now just tries to load a pom
> whose only content is a section to load
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/4/12 10:29 AM, Benjamin Reed wrote:
> ...am I doing something wrong? Seems like the test framework is
> breaking on the simplest things, I'm not sure how to start out if
> I can't even unit test this.
So in attempting to troubleshoot this, it a
I'm trying to write a maven plugin. I've added
maven-plugin-testing-harness to my project as a test dependency, and
created a very simple test that right now just tries to load a pom
whose only content is a section to load the plugin.
If I have it load like this:
> org.opennms.
The Maven team is pleased to announce the release of the Maven Plugin
Testing, version 2.0
The Maven Plugin Testing contains the necessary modules to be able to
test Maven Plugins.
http://maven.apache.org/plugin-testing/
org.apache.maven.plugin-testing
maven-plugin-testing
o do this?
>
> regards,
> Oliver
>
>
> Am 27.01.2011 um 22:41 schrieb Olivier Lamy:
>
>> Hello,
>> With maven3, you have to use
>>
>>
>> org.apache.maven.plugin-testing
>> maven-plugin-testing-harness
>> 2.0-alpha-
llo,
> With maven3, you have to use
>
>
> org.apache.maven.plugin-testing
> maven-plugin-testing-harness
> 2.0-alpha-1
> test
>
>
>
>
> 2011/1/27 oliver :
>> Hi,
>>
>> I'm working at a Maven plugin for OOo whi
Hello,
With maven3, you have to use
org.apache.maven.plugin-testing
maven-plugin-testing-harness
2.0-alpha-1
test
2011/1/27 oliver :
> Hi,
>
> I'm working at a Maven plugin for OOo which uses
> maven-plugin-testing-harness-1.2 for testing
Hi,
I'm working at a Maven plugin for OOo which uses
maven-plugin-testing-harness-1.2 for testing. With Maven-2 it works fine but
with Maven-3 I'll get a
java.lang.IllegalAccessError: tried to access field
org.codehaus.plexus.PlexusTestCase.container
maven-invoker-plugin its usually better for plugin testing. verifier is for
> writing plugin tests from eg junit. invoker works differently
>
> - Stephen
>
> ---
> Sent from my Android phone, so random spelling mistakes, random nonsense
> words and other nonsense are a direct re
maven-invoker-plugin its usually better for plugin testing. verifier is for
writing plugin tests from eg junit. invoker works differently
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on
Hi,
I tried the maven-verifier as described in
http://maven.apache.org/plugin-developers/plugin-testing.html. The expample
shows how an artifact can be deleted from the repository
(verifier.deleteArtifact(...)) but does not show how I can use my plugin for
testing. Or must I install it manuall
Hi All,
is the maven-plugin-testing-harness supposed to set the project field
of a mojo? Or shall we do it ourself?
Basically, I lookup the mojo and I get an instance of it; the mojo has
an instance field "project", but it does not get initialized. Is this
the normal behaviour?
Thanks
Hello Maven users,
If one installs a snapshot of a plugin (P1) in local repository, and for
other plugin (P2) an IT, run using maven-invoker-plugin configured as
recommended to use isolated local repository for integration tests, is a
project which makes use of P1 snapshot, IT will fail since P1 s
The Maven team is pleased to announce the release of the Maven Plugin
Testing, version 2.0-alpha-1.
This harness assists in creating unit or integration tests for Maven
plugins. See the component's site for more details:
http://maven.apache.org/plugin-testing/
This new version o
Hi there,
I was wondering why the latest CI snapshot of maven-plugin-testing was
out of date according to the source:
http://svn.apache.org/repos/asf/maven/plugin-testing/trunk/pom.xml
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugin-testing/maven-plugin
The Maven team is pleased to announce the release of the Maven Plugin
Testing, version 1.2
The Maven Plugin Testing contains the necessary modules to be able to
test Maven Plugins.
http://maven.apache.org/plugin-testing/
Note: This release changes the groupId for the artifacts.
You can specify
I started working with the maven-plugin-testing-harness and right now I am
looking for a way to stop the building of the plugin I am testing if the
harness has a failure. So basically I have a plugin A which I am testing with
the harness plugin. If the harness throws an assertion I want the
Hi all,
I am developing a plugin that copies some dependencies to a directory. I'm
doing this because I need to setup a server by copying some JARs to a
deployment directory.
I am having lots of problems understanding the different plugin testing
methods described on the page :
Hello,
I would like to know where I can find usage examples of the
maven-plugin-testing-tools shared component. It looks really
interesting
Thx
PS: Is it possible to connect to irc.codehaus.org using erc on emacs ?
I keep getting connection errors...
--
OQube < software engineering \ gé
Lately, I've been using the maven-plugin-testing-tools to create unit tests for
my plugins, and it works like a charm - mostly. However, I've discovered that I
can't get code coverage data using either Clover or Cobertura - they always
come up with 0% coverage.
Is this an inhe
his is a bug... Please file this in jira and we'll have a look at it.
>>>> Thanks.
>>>>
>>> What project, what component?
>>>
>>> Thanks,
>>>
>>> Jochen
>>>
>
franz see wrote:
Good day,
Re #1.
AFAIK, testing harness does not inject values for @parameter. You may want
to try something like
/**
* @component role="org.apache.maven.artifact.repository.ArtifactRepository"
*/
private ArtifactRepostiory localRepository;
I think this won't work. You
n jira and we'll have a look at it.
>> Thanks.
>
> What project, what component?
>
> Thanks,
>
> Jochen
>
> --
> How fast can a year go? As fast as your childs first year.
>
> ---------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For add
Hi, Edwin,
first of all, thanks for your reply.
On 2/11/07, Edwin Punzalan <[EMAIL PROTECTED]> wrote:
>How do I creare this parameter? I suppose, it's an instance of
> DefaultArtifactRepository,
>but how do I configure it?
I'm pretty sure the testing harness can take care of expression
Please see my inline comments below...
Jochen Wiedmann wrote:
Hi,
I am currently trying to use the maven-plugin-testing-harness for
testing a report plugin. Two questions came up so far:
1.) When I run the test, I receive the following exception:
java.lang.NullPointerException
Hi,
I am currently trying to use the maven-plugin-testing-harness for
testing a report plugin. Two questions came up so far:
1.) When I run the test, I receive the following exception:
java.lang.NullPointerException">java.lang.NullPointerException
Hi,
in order to fix some bugs in the javacc plugins JTBMojo, I wrote a
little integration test, based on the maven-plugin-testing-harness.
However, I am unable to get it running, because I always receive the
following error message:
[ERROR] Nonexistent component
this message in context:
http://www.nabble.com/maven-plugin-testing-harness%3A-getting-an-ArtifactRepository-for-my-test-tf2084342.html#a5758485
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PR
orObject, I think).
setVariableValueToObject. Thanks.
P.S. there is no javadoc report at
http://maven.apache.org/shared/maven-plugin-testing-harness. Would it be
easy to add it?
P.P.S. It's quite hard to find the URL above. Could someone put a link in
the main plugin API guide
(http://maven.apache.org/guides/pl
> However, if you prefer the private field injection you can also use
> the helpers in the abstract test case (setFieldForObject, I think).
setVariableValueToObject. Thanks.
P.S. there is no javadoc report at
http://maven.apache.org/shared/maven-plugin-testing-harness. Would it be
e
.
--
View this message in context:
http://www.nabble.com/maven-plugin-testing-harness%3A-getting-an-ArtifactRepository-for-my-test-tf2084342.html#a5744691
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail:
I could add setters for my mojo parameters.
--
View this message in context:
http://www.nabble.com/maven-plugin-testing-harness%3A-getting-an-ArtifactRepository-for-my-test-tf2084342.html#a5744691
Sent from the Maven - Users forum at
Ah, you might need to just steal the code then.
I see what you mean about getting it into a mojo - you'll need to set
it directly into there.
The plugin testing harness still needs some work...
- Brett
On 10/08/06, Dave Syer <[EMAIL PROTECTED]> wrote:
> Actually, I created
t case extends
PlexusTestCase I can't use it and the AbstractMojoTestCase together. Any
suggestions?
--
View this message in context:
http://www.nabble.com/maven-plugin-testing-harness%3A-getting-an-ArtifactRepository-for-my-test-tf2084342.html#a5744003
Sent from the Maven - Users
e ${basedir} in a parameter expression resolve? I find I
have to override all the parameters that contain ${basedir} in theor
expression separately.
--
View this message in context:
http://www.nabble.com/maven-plugin-testing-harness%3A-getting-an-ArtifactRepository-for-my-test-tf2084342.html#a5
-plugin-testing-harness%3A-getting-an-ArtifactRepository-for-my-test-tf2084342.html#a5743139
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
sedir} to be the directory where the pom.xml is.
Jesse McConnell wrote:
org.apache.maven.shared
maven-plugin-testing-harness
1.0-beta-1
test
http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Harness
I originally put this harness together with help from jason so that we
Jesse McConnell wrote:
org.apache.maven.shared
maven-plugin-testing-harness
1.0-beta-1
test
http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Harness
I originally put this harness together with help from jason so that we
could instantiate mojo's easily in test case
org.apache.maven.shared
maven-plugin-testing-harness
1.0-beta-1
test
http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Harness
I originally put this harness together with help from jason so that we
could instantiate mojo's easily in test cases and feed in
configur
Jochen Wiedmann wrote:
On 6/21/06, Maria Odea Ching <[EMAIL PROTECTED]> wrote:
Did you check that you have the correct goal name when you looked up the
mojo? :)
There seems to be nothing wrong with your configuration..
That's been the problem when you wrote me the last time, wasn't it?
:-)
On 6/21/06, Maria Odea Ching <[EMAIL PROTECTED]> wrote:
Did you check that you have the correct goal name when you looked up the
mojo? :)
There seems to be nothing wrong with your configuration..
That's been the problem when you wrote me the last time, wasn't it?
:-) But test-jar is right, isn
Hi Jochen,
Did you check that you have the correct goal name when you looked up the
mojo? :)
There seems to be nothing wrong with your configuration..
Thanks,
Odea
Jochen Wiedmann wrote:
Hi,
I am about to write a test case for MJAR-20. Below you find my unit test and
my pom. Unfortunately,
Hi,
I am about to write a test case for MJAR-20. Below you find my unit test and
my pom. Unfortunately, when I try to execute the unit test, I receive the
following exception:
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Component descriptor cannot be found in the
Olivier Lamy wrote:
> setVariableValueToObject( vm , "basedir", new File( getBasedir() ) );
> Before vm.execute();
Thanks, that worked like a charm!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [
1
À : Maven Users List
Objet : More questions on maven-plugin-testing-harness
Hi,
thanks to Odea's help, I managed to get a few steps further. However, I
have
to return with another question in the end.
My plugin contains the following variable:
/**
* The base director
Hi,
thanks to Odea's help, I managed to get a few steps further. However, I have
to return with another question in the end.
My plugin contains the following variable:
/**
* The base directory, relative to which directory names are
* interpreted.
*
* @parameter expressio
Maria Odea Ching wrote:
> I don't think you need to include the goalPrefix ("xml") when you lookup
> the mojo in your test case
> when you use the testing harness.
>
> It should be:
>
> ValidatorMojo vm = (ValidatorMojo) lookupMojo( "validate", testPom );
Thanks, that worked!
Jochen
---
e:
Hi,
I am attempting to write a plugin test by using the
maven-plugin-testing-harness. I have created the following test-POM and am
trying to invoke it through
File testPom = new File( getBasedir(), "src/test/it1/pom.xml" );
ValidatorMojo vm = (ValidatorMojo) lookupMojo( "xml:v
Hi,
I am attempting to write a plugin test by using the
maven-plugin-testing-harness. I have created the following test-POM and am
trying to invoke it through
File testPom = new File( getBasedir(), "src/test/it1/pom.xml" );
ValidatorMojo vm = (ValidatorMojo) lookupMojo( &qu
87 matches
Mail list logo
