nrepository.com/artifact/org.apache.maven.plugin-testing/maven-plugin-testing-harness
seems very old or is there also a new GAV?
No, this is up to date.
Am 27.09.22 um 16:43 schrieb Slawomir Jaranowski:
wt., 27 wrz 2022 o 16:31 Christoph Läubrich
napisał(a):
I recently came across a problem
changes seem to be mostly dependency and doc updates.
>
>
> https://mvnrepository.com/artifact/org.apache.maven.plugin-testing/maven-plugin-testing-harness
>
> seems very old or is there also a new GAV?
>
No, this is up to date.
>
> Am 27.09.22 um 16:43 schrieb Slawom
Thanks for the updated references, one of the issues seems already be
addressed, are there any plans for a release?
https://mvnrepository.com/artifact/org.apache.maven.plugin-testing/maven-plugin-testing-harness
seems very old or is there also a new GAV?
Am 27.09.22 um 16:43 schrieb Slawomir
wt., 27 wrz 2022 o 16:31 Christoph Läubrich
napisał(a):
> I recently came across a problem with the
> maven-plugin-testing-harness[1] and wanted to report a bug, but without
> success.
>
>
> https://maven.apache.org/plugin-testing/maven-plugin-testing-harness/issue-tracking.h
I recently came across a problem with the
maven-plugin-testing-harness[1] and wanted to report a bug, but without
success.
https://maven.apache.org/plugin-testing/maven-plugin-testing-harness/issue-tracking.html
-> dead link
https://maven.apache.org/plugin-testing/maven-plugin-test
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
dependabot[bot] commented on pull request #44:
URL: https://github.com/apache/maven-site-plugin/pull/44#issuecomment-813642866
OK, I won't notify you again about this release, but will get in touch when
a new version is available.
If you change your mind, just re-open this PR and I'l
asfgit closed pull request #44:
URL: https://github.com/apache/maven-site-plugin/pull/44
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, p
dependabot[bot] opened a new pull request #44:
URL: https://github.com/apache/maven-site-plugin/pull/44
Bumps
[maven-plugin-testing-harness](https://github.com/apache/maven-plugin-testing)
from 2.1 to 3.3.0.
Commits
https://github.com/apache/maven-plugin-testing/commit
ating plugin to 3.0.0 and I have a problem with a test
> > because it fails due to maven-plugin-testing-harness:3.0.0 cannot call a
> > method:
> >
> setClassPathScanning(Ljava/lang/String;)Lorg/codehaus/plexus/ContainerConfiguration;
> >
> > In maven-plugin-testing-h
> > because it fails due to maven-plugin-testing-harness:3.0.0 cannot call a
> > method:
> >
> > setClassPathScanning(Ljava/lang/String;)Lorg/codehaus/plexus/ContainerConfiguration;
> >
> > In maven-plugin-testing-harness' code the method setClassPathScanning
.
That said I would have assumed the maven-plugin-testing-harness would fully
isolate the runtime being tested from the harness so you wouldn’t need to do
this.
PS. which plugin are you migrating?
On Thursday, 7 January 2016 at 12:40, Tibor Digana wrote:
> I am migrating plugin to 3.0.0 an
hole thing is a mess would be an
> understatement ;-)
>
> On 7 January 2016 at 12:40, Tibor Digana <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=5858236&i=0>>
> wrote:
>
> > I am migrating plugin to 3.0.0 and I have a problem with a test
>
gt; I am migrating plugin to 3.0.0 and I have a problem with a test
> because it fails due to maven-plugin-testing-harness:3.0.0 cannot call a
> method:
>
> setClassPathScanning(Ljava/lang/String;)Lorg/codehaus/plexus/ContainerConfiguration;
>
> In maven-plugin-testin
I am migrating plugin to 3.0.0 and I have a problem with a test
because it fails due to maven-plugin-testing-harness:3.0.0 cannot call a
method:
setClassPathScanning(Ljava/lang/String;)Lorg/codehaus/plexus/ContainerConfiguration;
In maven-plugin-testing-harness' code the m
Sounds reasonable.
On Jul 2, 2014, at 4:04 PM, Igor Fedorenko wrote:
> SessionScope and MojoExecutionScope introduced in maven 3.2.1 require
> explicit support from maven-plugin-testing-harness. Unfortunately, there
> is no clean/straightforward way to introduce such support and still
SessionScope and MojoExecutionScope introduced in maven 3.2.1 require
explicit support from maven-plugin-testing-harness. Unfortunately, there
is no clean/straightforward way to introduce such support and still be
able to use maven-plugin-testing-harness with earlier versions of maven.
What
On Sun, Jun 5, 2011 at 7:30 AM, Benson Margulies wrote:
> Sure, for an integration test. I was striving for a smaller-scale unit
> test. I even succeeded :-)
Since you originally requested the example and now have success, can
you provide a link to how you did it?
Do we even have this stuff capt
On Sat, Jun 4, 2011 at 4:16 PM, Olivier Lamy wrote:
> Hello,
> Perso, I usually use invoker plugin (more easy to test with various
> maven core version)
>
Sure, for an integration test. I was striving for a smaller-scale unit
test. I even succeeded :-)
> 2011/6/4 Benson Margulies :
>> Anyone got
Hello,
Perso, I usually use invoker plugin (more easy to test with various
maven core version)
2011/6/4 Benson Margulies :
> Anyone got an example of using the harness on a reporting plugin? I'm
> a bit stalled when the mock project can't resolve the skin.
>
> -
Anyone got an example of using the harness on a reporting plugin? I'm
a bit stalled when the mock project can't resolve the skin.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...
I answered my own question. I added this method to my test case which
extends AbstractMojoTestCase:
protected Settings getSettings() throws Exception {
DefaultSettingsBuilderFactory defaultSettingsBuilderFactory = new
DefaultSettingsBuilderFactory();
DefaultSettingsBuilder settingsBuilde
Hello Maven Developers,
I am using the maven-plugin-test-harness-2.0-alpha-1 and creating JUnit
tests for a plugin I am developing. I am able to test my Mojos but I am
currently hardcoding some values into my tests such as command paths. This
configuration is configured in my settings.xml. Is th
ly 14, 2008 9:33 AM
> To: Maven Developers List
> Subject: Releasing maven-plugin-testing-harness?
>
> The deploy plugin has a snapshot dependency on
> maven-plugin-testing-harness, which is preventing a release. That
> artifact seems to have moved...
>
> The current dep
It did move, I say release it, it's mostly an internal dependency
anyway.
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Monday, July 14, 2008 9:33 AM
To: Maven Developers List
Subject: Releasing maven-plugin-testing-harness?
The deploy plugin has a sna
On Mon, Jul 14, 2008 at 8:15 AM, Vincent Siveton
<[EMAIL PROTECTED]> wrote:
> maven-plugin-testing-harness:2.4-SNAPSHOT [1] is the old version
> before applying [2].
> A new snapshot is already present in [3].
>
> Feel free to release it.
I'll update the dependency in
Hi Wendy,
maven-plugin-testing-harness:2.4-SNAPSHOT [1] is the old version
before applying [2].
A new snapshot is already present in [3].
Feel free to release it.
Cheers,
Vincent
[1]
http://people.apache.org/maven-snapshot-repository/org/apache/maven/maven-plugin-testing-harness/2.4-SNAPSHOT
The deploy plugin has a snapshot dependency on
maven-plugin-testing-harness, which is preventing a release. That
artifact seems to have moved...
The current dependency is: on
org.apache.maven:maven-plugin-testing-harness:2.4-SNAPSHOT, but I
don't see that anywhere.
I think it has mov
The deploy plugin has a snapshot dependency on
maven-plugin-testing-harness, which is preventing a release. That
artifact seems to have moved...
The current dependency is: on
org.apache.maven:maven-plugin-testing-harness:2.4-SNAPSHOT, but I
don't see that anywhere.
I think it has mov
On 30/12/2007, at 2:44 PM, Brian E. Fox wrote:
Hi Nick, I'm working on fixing these issues. I was unaware that the
harness got moved to a new tlp "plugin-tools"
They all now have a common version, so it's more complicated to
release
this. Anyone know why this was moved? (Brett?)
Just thou
Brian
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 20, 2007 10:03 AM
To: Maven Developers List
Subject: RE: Bugs in maven-plugin-testing-harness
Hi Nick,
That factory came from the dependency plugin so I'll fix the bugs. I
need to release
: dev@maven.apache.org
Subject: Bugs in maven-plugin-testing-harness
Hi,
I am writing a rule for the enforcer plugin and was using the
maven-plugin-testing-harness classes. (Just like the testing code for
the other rules)
Now I've found two small bugs in this code. Is this still maintained?
The website
Hi,
I am writing a rule for the enforcer plugin and was using the
maven-plugin-testing-harness classes. (Just like the testing code for the other
rules)
Now I've found two small bugs in this code. Is this still maintained? The
website [1] hasn't been updated for more then a year,
lugin-testing-harness 1.1
There have been tons of enhancements to the plugin testing harness since
the last release in April. Several plugins require the new version
before release.
Tag:
https://svn.apache.org/repos/asf/maven/shared/tags/maven-plugin-testing-
harness-1.1
Staged at:
lease.
>
>
>
> Tag:
>
> https://svn.apache.org/repos/asf/maven/shared/tags/maven-plugin-
> testing-
> harness-1.1
>
>
>
> Staged at:
>
> http://people.apache.org/~brianf/staging-repository
>
>
>
> Vote
+1
On 9 Jul 2007, at 00:37, Brian E. Fox wrote:
There have been tons of enhancements to the plugin testing harness
since
the last release in April. Several plugins require the new version
before release.
Tag:
https://svn.apache.org/repos/asf/maven/shared/tags/maven-plugin-
testing
he new version
before release.
Tag:
https://svn.apache.org/repos/asf/maven/shared/tags/maven-plugin-testing-
harness-1.1
Staged at:
http://people.apache.org/~brianf/staging-repository
Vote is open for 72hrs, please +1/+0/-1
+1
Thanks,
+1
On 8 Jul 07, at 4:37 PM 8 Jul 07, Brian E. Fox wrote:
There have been tons of enhancements to the plugin testing harness
since
the last release in April. Several plugins require the new version
before release.
Tag:
https://svn.apache.org/repos/asf/maven/shared/tags/maven-plugin
There have been tons of enhancements to the plugin testing harness since
the last release in April. Several plugins require the new version
before release.
Tag:
https://svn.apache.org/repos/asf/maven/shared/tags/maven-plugin-testing-
harness-1.1
Staged at:
http://people.apache.org
> Sanchez
> Sent: Friday, April 13, 2007 5:13 PM
> To: Maven Developers List
> Subject: Re: [VOTE] Release maven-plugin-testing-harness
>
> anyone?
>
> On 4/10/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> > It adds some stub method implementations from prev
As some one who has just picked up the maven-plugin-testing-harness and is
attempting to use it I think it would be *really* useful to include a brief
explanation on what the harness does and doesn't do. Eg can it provide a
Mojo with injected depencies and if so how?
A brief example on ho
+1
Vincent
2007/4/13, Brian E. Fox <[EMAIL PROTECTED]>:
+1
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: Friday, April 13, 2007 5:13 PM
To: Maven Developers List
Subject: Re: [VOTE] Release maven-plugin-testing-harness
+1
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: Friday, April 13, 2007 5:13 PM
To: Maven Developers List
Subject: Re: [VOTE] Release maven-plugin-testing-harness
anyone?
On 4/10/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote
ases
> >
> > Right now it's 1.0-beta-2 but has been pretty stable during last year,
> > so i'd suggest releasing 1.0 and whatever is added in the future go to
> > 1.1, 1.2, ...
> >
> >
>
https://svn.apache.org/repos/asf/maven/shared/trunk/maven-pl
ast year,
> so i'd suggest releasing 1.0 and whatever is added in the future go to
> 1.1, 1.2, ...
>
>
https://svn.apache.org/repos/asf/maven/shared/trunk/maven-plugin-testing-harness
> 527389
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too
1.2, ...
https://svn.apache.org/repos/asf/maven/shared/trunk/maven-plugin-testing-harness
527389
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
--
I could give you my word as a Spaniard.
No good. I'v
It adds some stub method implementations from previous releases
Right now it's 1.0-beta-2 but has been pretty stable during last year,
so i'd suggest releasing 1.0 and whatever is added in the future go to
1.1, 1.2, ...
https://svn.apache.org/repos/asf/maven/shared/trunk/maven-plug
t; <[EMAIL PROTECTED]>
To: "Maven Developers List"
Sent: Monday, December 18, 2006 9:20 AM
Subject: [M2][maven-plugin-testing-harness] Lookup for custom Mocks
Hi,
In a plugin i experiment with the testing harness.
I would like to know how to configure the remote repositories and
Hi,
In a plugin i experiment with the testing harness.
I would like to know how to configure the remote repositories and settings
file.
The plugin should be run in a directory without a pom.xml file.
Regards,
Raphaël
50 matches
Mail list logo
