:
> 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/m
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
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
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:
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.
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/45241317/hard-time-
> mojo-testing-wit
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
pache.org/jira/browse/INFRA-14716
As far as I can tell, the fix didn't work. I updated the JIRA issue but I
was unable to re-open the ticket and I could only leave "internal comments"
which aren't publicly visible, despite logging in.
What would also be incredibly useful is a link to th
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-harness, I'm
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/browse
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 which
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 maven
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 goal
On 2015-11-13T18:04:01 -0500
Jason van Zyl wrote:
> 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:
>
>
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:
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
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
'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:
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
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,
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-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
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 plugin section to load the plugin.
If I have it load like this:
plugin
-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
lundi 4 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 plugin section to load the plugin
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 from class
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 from class
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 from class
org.apache.maven.plugin.testing.AbstractMojoTestCase
/scope
/dependency
2011/1/27 oliver oliver.bo...@gmail.com:
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
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 in advance
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
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
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 expressions
]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Two-questions-on-maven-plugin-testing-harness-tf3203630s177.html#a8917713
Sent from the Maven - Users mailing list archive at Nabble.com
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
]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Two-questions-on-maven-plugin-testing-harness-tf3203630s177.html#a8917993
Sent from the Maven - Users mailing list archive
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.NullPointerExceptionjava.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
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
easy
. 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/plugin/guide-java-plugin
:
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 PROTECTED]
For additional
-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
} 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#a5743139
Sent from
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 forum at Nabble.com
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 forum at Nabble.com
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 Nabble.com
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: [EMAIL PROTECTED
Maybe if the test-harness can be provided with a pom.xml file and from
there it can build several of the needed expressions. Of course, the
plugin configuration should already be in the pom so we need not provide
two separate files for the test-harness. I'd also suggest parsing
${basedir}
dependency
groupIdorg.apache.maven.shared/groupId
artifactIdmaven-plugin-testing-harness/artifactId
version1.0-beta-1/version
scopetest/scope
/dependency
http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Harness
I originally put this harness together with help from jason
Jesse McConnell wrote:
dependency
groupIdorg.apache.maven.shared/groupId
artifactIdmaven-plugin-testing-harness/artifactId
version1.0-beta-1/version
scopetest/scope
/dependency
http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Harness
I originally put this harness
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:validate, testPom );
vm.execute();
But I
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
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
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 directory, relative to which directory names are
* interpreted
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:
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:validate, testPom
58 matches
Mail list logo