Just curious, why is such an old version of maven-dependency-plugin used in
that build?
- Eric L
On Sat, Feb 25, 2023 at 2:46 PM Elliotte Rusty Harold
wrote:
> On Sat, Feb 25, 2023 at 11:46 AM Guillaume Nodet
> wrote:
> >
> > Which goal are you running ?
> > I think you need to run the package
On Sat, Feb 25, 2023 at 11:46 AM Guillaume Nodet wrote:
>
> Which goal are you running ?
> I think you need to run the package phase as hinted by the error.
>
mvn test
also
mvn compile; mvn test
mvn clean test
mvn package; mvn test
All end with the same failure. This seems to be a regression
Which goal are you running ?
I think you need to run the package phase as hinted by the error.
Le sam. 25 févr. 2023 à 07:58, Elliotte Rusty Harold a
écrit :
> FYI, maven core tests fail for me (Java 1.8. Maven 3.8.7) when
> building at head like so. I'm not sure what to do about this:
>
> [INFO
Stephen Connolly wrote:
> Here is the test plan.
>
> 1. We (=benjamin) run all the builds that are currently working with
> m3+plugin-enfocer+new surefire plugin -SNAPHOT. If all builds still
> pass with the new surefire plugin, then we say all is good
>
> 2. If all is good, we (=benjamin or me
Please put them in if you don't mind. I seem to remember that at least
one int-test was missing the license even before I added my additional
test. I will add the license plugin to idea :)
Kristian
Den 4. jan. 2010 kl. 10.50 skrev Stephen Connolly
:
> SUREFIRE-555 looks good.
>
> I just have som
On 2010-01-04, at 4:50 AM, Stephen Connolly wrote:
> SUREFIRE-555 looks good.
>
> I just have some questions w.r.t. the licensing
>
> Some of the integration test java classes do not seem to have the ASL
> header... does this matter?
>
Kristian will likely have a CLA on file shortly. You can p
SUREFIRE-555 looks good.
I just have some questions w.r.t. the licensing
Some of the integration test java classes do not seem to have the ASL
header... does this matter?
-Stephen
2010/1/4 Stephen Connolly :
> will do
>
> Sent from my [rhymes with tryPod] ;-)
>
> On 3 Jan 2010, at 23:45, Brett
will do
Sent from my [rhymes with tryPod] ;-)
On 3 Jan 2010, at 23:45, Brett Porter wrote:
There was a patch (SUREFIRE-555) by Kristian that looked good, but I
didn't get time to look at it in detail and apply/test it. If you
have time to do that while you are doing the testing that'd be g
There was a patch (SUREFIRE-555) by Kristian that looked good, but I didn't get
time to look at it in detail and apply/test it. If you have time to do that
while you are doing the testing that'd be great.
- Brett
On 02/01/2010, at 10:47 PM, Stephen Connolly wrote:
> Here is the test plan.
>
http://jira.codehaus.org/browse/SUREFIRE-584
2010/1/3 Stephen Connolly :
> OK, Surefire is currently un-releaseable due to how the integration
> tests are written.
>
> I will start reworking them tomorrow.
>
> I will also merge failsafe's goals into surefire since I'm touching the code
>
> Once I
OK, Surefire is currently un-releaseable due to how the integration
tests are written.
I will start reworking them tomorrow.
I will also merge failsafe's goals into surefire since I'm touching the code
Once I have fixed things then I will roll the release
-Stephen
2010/1/2 Stephen Connolly :
>
I am going to merge the two together, but i'd like to get 2.5 out first
2010/1/2 Paul Benedict :
> I remember hearing about the fail-safe plugin... Are you going to
> merge into surefire? I think the best choice is to eliminate competing
> plug-ins and aggregating new functionality in one.
>
> Pau
I remember hearing about the fail-safe plugin... Are you going to
merge into surefire? I think the best choice is to eliminate competing
plug-ins and aggregating new functionality in one.
Paul
On Sat, Jan 2, 2010 at 6:25 AM, Stephen Connolly
wrote:
> i'm fine with moving my code from mojo to mav
i'm fine with moving my code from mojo to maven... when I wrote
failsafe I was not an apache committer...
I'd like to sort out scoping toolchains before doing that though
so I was thinking 2.6 could be the merged version
I'd plan on pushing 2.6 in a month or so (i.e. before m3)
-Stephen
2010/1/
And what about the failsafe plugin
This one is very useful and is a copy of surefire dedicated to its with
junit.
Couldn't we move it to Apache and use a shared lib to update them all
together ?
Couldn't we integrate it by default in maven 3 in the lifecycle ?
WDYT ?
Arnaud Héritier
Software Fact
It may be worth to release both at the same time with new surefire
plugin in the test, of course maven-compiler-plugin are good to go
first( seem you are already did it )
-D
On Tue, Dec 29, 2009 at 5:49 PM, Stephen Connolly
wrote:
> I was going to ask the same question myself
>
> Sent from my [r
I was going to ask the same question myself
Sent from my [rhymes with tryPod] ;-)
On 30 Dec 2009, at 01:05, Brett Porter wrote:
On 30/12/2009, at 6:38 AM, Stephen Connolly wrote:
I don't have the permissions on plexus (AFAIK) if somebody else
wants to do
that, then yes, I will wait (until
On 30/12/2009, at 3:22 AM, Stephen Connolly wrote:
> Are we sure that the toolchains stuff has made it into surefire 2.5-SNAPSHOT
> yet?
Yes. It was in 2.4.3 :)
The only other changes are:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+SUREFIRE+AND+fixVersi
On 30/12/2009, at 6:38 AM, Stephen Connolly wrote:
> I don't have the permissions on plexus (AFAIK) if somebody else wants to do
> that, then yes, I will wait (until the end of the week providing that I am
> told the release will be pushed this week... or if somebody wants to grant
> me permisson
cool
Sent from my [rhymes with tryPod] ;-)
On 29 Dec 2009, at 20:15, Olivier Lamy wrote:
Ok.
I think I have karma for this : I will release plexus-compiler.
--
Olivier
2009/12/29 Stephen Connolly :
I don't have the permissions on plexus (AFAIK) if somebody else
wants to do
that, then yes,
Ok.
I think I have karma for this : I will release plexus-compiler.
--
Olivier
2009/12/29 Stephen Connolly :
> I don't have the permissions on plexus (AFAIK) if somebody else wants to do
> that, then yes, I will wait (until the end of the week providing that I am
> told the release will be pushed
I don't have the permissions on plexus (AFAIK) if somebody else wants to do
that, then yes, I will wait (until the end of the week providing that I am
told the release will be pushed this week... or if somebody wants to grant
me permissons on plexus, I will push the release myself, but seriously, w
Hi,
Is-it possible to release plexus-compiler first and re re run with the
released version ?
--
Olivier
2009/12/29 Stephen Connolly :
> 2009/12/29 Stephen Connolly
>
>>
>>
>> 2009/12/29 Stephen Connolly
>>
>>> Follow on from:
>>> http://old.nabble.com/What%27s-blocking-releasing-maven-compiler
2009/12/29 Stephen Connolly
>
>
> 2009/12/29 Stephen Connolly
>
>> Follow on from:
>> http://old.nabble.com/What%27s-blocking-releasing-maven-compiler-plugin--td26154745.html#a26156747
>>
>>
>> Here is my proposal of the test plan.
>>
>> 1. We (=benjamin) set up the grid @ sonatype to use the
>>
2009/12/29 Brett Porter
>
> On 29/12/2009, at 11:27 PM, Stephen Connolly wrote:
>
> > Any body got any objections / additional test cases to add?
>
> What about testing with Maven 2.2.1? Maybe even Maven 2.0.8 since they'll
> get autoupgraded (yah, I know it's an old version).
>
>
1. if the pom i
On 29/12/2009, at 11:27 PM, Stephen Connolly wrote:
> Any body got any objections / additional test cases to add?
What about testing with Maven 2.2.1? Maybe even Maven 2.0.8 since they'll get
autoupgraded (yah, I know it's an old version).
> P.S. we should re-use this test plan for surefire
I
2009/12/29 Stephen Connolly
> Follow on from:
> http://old.nabble.com/What%27s-blocking-releasing-maven-compiler-plugin--td26154745.html#a26156747
>
> Here is my proposal of the test plan.
>
> 1. We (=benjamin) set up the grid @ sonatype to use the
> maven-plugin-enforcer (
> https://svn.apache.o
I'm wondering if we need m3-alpha-6 before starting this plan? or can we run
with m3-alpha-5
2009/12/29 Stephen Connolly
> Follow on from:
> http://old.nabble.com/What%27s-blocking-releasing-maven-compiler-plugin--td26154745.html#a26156747
>
> Here is my proposal of the test plan.
>
> 1. We (=be
You're welcome ;-)
-Stephen
2008/11/10 Jason van Zyl <[EMAIL PROTECTED]>
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder, Apache Maven
> jason at sonatype dot com
> --
>
> You
Yep, it's fine in Continuum and when I build on Linux as well. Just
looking to see if anyone else was getting them.
Actually, it could be related to MNG-3419. I'm not sure why I'm
getting the OOME in the first place though.
Will keep digging later.
On 26/02/2008, at 6:19 AM, Jason van Zyl
Looks to be chugging along happily. I'll do another clean build but
Hudson is usually accurate now:
http://people.apache.org/~jvanzyl/happy_booty.txt
On 24-Feb-08, at 9:54 PM, Brett Porter wrote:
Is anyone else seeing these?
[java] Failed tests:
[java]
testReportInvalidPluginFor
Hi,
2008/2/20, Wendy Smoak <[EMAIL PROTECTED]>:
> It looks like some changes in maven-plugin-testing-harness caused
> errors in the tests in the Install plugin. This is the first build
> that shows the problem:
>
> http://maven.zones.apache.org/continuum/buildResult.action?buildId=39712&proje
dfabulich wrote:
>
> Inter-class dependencies are one of TestNG's fundamental features
>
Use of this feature is optional. For my sake, call it an "abuse" of TestNG
if I run that simple unit tests without inter-class dependencies ;-)
dfabulich wrote:
>
> [...] but TestNG is meant to support
Jason van Zyl wrote:
Correct me if I'm wrong here Benjamin but I think he's talking about
stating what tests you want to run, and how they are grouped
declaratively. As a best practice don't use suites and come up with a
way in Surefire to group things and avoid grouping of things in code.
I
Benjamin Bentmann wrote:
I see. Now, if the user can provide an option to Surefire, indicating
that the unit tests do not have inter-class dependencies, wouldn't this
allow to get back the old behavior? I.e. enabling Surefire to pass test
classes individually into TestNG?
That option sounds
dfabulich wrote:
>
> Typically it's used for slow tests; you can identify a subset of tests
> that you want to run and just run those. (You can even pull just one
> method from Class X, and another method from Class Y, and so on.)
>
Thanks for the explanation. To me, this seems more useful f
Steve Loughran wrote:
What I propose is that, in order to avoid destroying information, Surefire
should generate XML that looks like Example 7 (all-in-one-file), and not
try to fake it to look like Example 2 (one-file-per-class). (TestNG's
junit-like output also generates files like Example 7.)
Benjamin Bentmann wrote:
For my curiosity: What would be the benefit of setting up a hand-crafted
test suite? I am a lazy guy and prefer the dumb machine to do the nasty
things for me so I really like the idea of just dropping a test class into
src/test/java without bothering to additionally mai
This is a user list question.
But the answer is plugin executions.
--
Eric Redmond
http://blog.propellors.net
On 8/2/07, Sergey Kabashnyuk <[EMAIL PROTECTED]> wrote:
>
> I mean to run all tests in one comand mvn clean test
> in one maven-surefire-plugin configuration.
> Can you show an example
I mean to run all tests in one comand mvn clean test
in one maven-surefire-plugin configuration.
Can you show an example?
you can configure as much folders as you want , just point maven
configuration to destination
thanks,
DT
www.ejinz.com
Search Engine News
- Original Message - Fro
you can configure as much folders as you want , just point maven
configuration to destination
thanks,
DT
www.ejinz.com
Search Engine News
- Original Message -
From: "Sergey Kabashnyuk" <[EMAIL PROTECTED]>
To:
Sent: Thursday, August 02, 2007 2:33 AM
Subject: Test dir
HI ALL
I have
Thanks.
On 3/29/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
I added the jvm memory option to the surefire plugin because now I have
this pb too :(
Emmanuel
Thierry Lach a écrit :
> I agree. I don't want to have to bump up my memory config for all
projects
> just because of one.
>
> On 3/
I added the jvm memory option to the surefire plugin because now I have this pb
too :(
Emmanuel
Thierry Lach a écrit :
I agree. I don't want to have to bump up my memory config for all projects
just because of one.
On 3/23/07, Andrew Williams <[EMAIL PROTECTED]> wrote:
I think that modifyi
I assumed that there was a leak or something weird and that it would
get addressed.
I have certainly seen it compile and test fine without it before,
recently too, so I know it is possible...
Andy
On 22 Mar 2007, at 15:46, Thierry Lach wrote:
Any reason why this couldn't just be added perm
Jesse McConnell wrote:
most people I know just add the following to their environment variables
MAVEN_OPTS=-Xmx512m
It shouldn't be necessary to have to patch your environment to work
around bugs in unit tests, if the tests need 512MB of RAM, then the
surefire plugin should be configured to
most people I know just add the following to their environment variables
MAVEN_OPTS=-Xmx512m
jesse
On 3/22/07, Thierry Lach <[EMAIL PROTECTED]> wrote:
Any reason why this couldn't just be added permanently?
On 3/22/07, Andrew Williams <[EMAIL PROTECTED]> wrote:
>
> I sometimes get that proble
Any reason why this couldn't just be added permanently?
On 3/22/07, Andrew Williams <[EMAIL PROTECTED]> wrote:
I sometimes get that problem too, when I see it I insert the
following into the section of continuum's root pom.xml
org.apache.maven.plugins
maven-sur
I sometimes get that problem too, when I see it I insert the
following into the section of continuum's root pom.xml
org.apache.maven.plugins
maven-surefire-plugin
-Xmx512m
org.apache.maven.plugins
maven-compi
im not sure but i think in order to change the amount of memory the
tests can use, you have to configure the surefire plugin - changing
the amount of memory maven uses dont take effect on tests (i think
they are ran on a separate jvm)
On 3/19/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
it's
it's set in MAVEN_OPTS env var with -Xmx and -Xms java options, but if you
don't know it, you probably use the default jvm options. You can try to it to
something like that:
MAVEN_OPTS=-Xmx256m
If you don't want to patch Continuum, you can use a prebuilt snapshot:
http://maven.zones.apache.org
Emmanuel Venisse wrote:
how many memory is allocated to the build? Normally the default is enough.
No idea - checked out a pristine copy of trunk as of an hour or two ago,
and did an mvn install.
Is there somewhere where memory allocations are set, perhaps in a pom file?
Regards,
Graham
--
how many memory is allocated to the build? Normally the default is enough.
Graham Leggett a écrit :
Emmanuel Venisse wrote:
jdk version?
Latest MacOSX version, jdk v1.5.0_07-164.
Regards,
Graham
--
Emmanuel Venisse wrote:
jdk version?
Latest MacOSX version, jdk v1.5.0_07-164.
Regards,
Graham
--
smime.p7s
Description: S/MIME Cryptographic Signature
jdk version?
Graham Leggett a écrit :
Hi all,
While trying to build trunk of continuum, I am getting the following
test failure on MacosX v10.4:
---
Test set:
org.apache.maven.continuum.buildcontroller.DefaultBuil
Stephane Nicoll wrote:
I don't think so. sources and ear are for sure good candidates since I
wrote those tests. At some point, we decided to use that testing
technique and fix remaining issues (namely the local repo first
install story).
We need to discuss this because I'd like to work on the
Wendy Smoak wrote:
On 3/14/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
The problem is that it uses the Verifier to test.
The Verifier uses the plugin from the local repo, not the current
project.
First, mvn clean install -Dmaven.test.skip=true, then mvn test and
it'll work.
I noticed th
I don't think so. sources and ear are for sure good candidates since I
wrote those tests. At some point, we decided to use that testing
technique and fix remaining issues (namely the local repo first
install story).
We need to discuss this because I'd like to work on the WAR plugin but
I want mor
On 3/14/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
The problem is that it uses the Verifier to test.
The Verifier uses the plugin from the local repo, not the current project.
First, mvn clean install -Dmaven.test.skip=true, then mvn test and it'll work.
I noticed this today.. there's about
The problem is that it uses the Verifier to test.
The Verifier uses the plugin from the local repo, not the current project.
First, mvn clean install -Dmaven.test.skip=true, then mvn test and it'll work.
I noticed this today.. there's about 4 plugins that won't install cleanly
because of this.
-
On 13 Mar 07, at 1:30 AM 13 Mar 07, Stephane Nicoll wrote:
Weird. Can you paste the surefire logs please?
I believe they are caused by the testing harness. I too get failures
but have been using it to make the embedder source jar for 10 bundles
or so. I was just going to switch it off th
Weird. Can you paste the surefire logs please?
On 3/13/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
I'm seeing test failures in maven-source-plugin. Anyone else?
On Windows w/ Maven 2.0.5:
Failed tests:
testProject003(org.apache.maven.plugin.source.SourceJarMojoTest)
testProject007(org.apac
Good day to you, Wendy,
On Windows XP, Maven 2.0.5, maven-source-plugin -r517268 builds fine
Cheers,
Franz
On 3/12/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
I'm seeing test failures in maven-source-plugin. Anyone else?
On Windows w/ Maven 2.0.5:
Failed tests:
testProject003(org.apache.ma
On 10/30/06, Philippe Faes <[EMAIL PROTECTED]> wrote:
Looks like the path to work-dir gets messed up. I'll give it a try on a
cygwin machine tomorrow. Today I have a deadline.
Are any other cygwin users getting the same problem?
Wendy, can you add your comments to CONTINUUM-968?
Done, though I
Looks like the path to work-dir gets messed up. I'll give it a try on a
cygwin machine tomorrow. Today I have a deadline.
Are any other cygwin users getting the same problem?
Wendy, can you add your comments to CONTINUUM-968?
grtz
Philippe
On Fri, 2006-10-27 at 09:06 -0700, Wendy Smoak wrote:
>
On 10/27/06, Edwin Punzalan <[EMAIL PROTECTED]> wrote:
Did that failure just return? I tried building it and I didn't get the
failure. I remember evenisse fixed something like this.
I've never been able to build Continuum without skipping the tests (in
continuum-release).
Again, was probab
Did that failure just return? I tried building it and I didn't get the
failure. I remember evenisse fixed something like this.
Again, was probably caused by the outdated snapshot repo, this time for
the maven-scm. Installing maven-scm locally should do the trick.
And again, someone should
See the post with the subject "unit testing headache" the stack trace is
in the message.
as far as I can tell, JPOX is complaining about the combination of
attributes.
- Brill Pappin
Emmanuel Venisse wrote:
Everyday, we build continuum with a clean checkout and a clean repo.
The build is ok
Everyday, we build continuum with a clean checkout and a clean repo. The build is ok without test
failure.
Can you send us the error?
Emmanuel
Brill Pappin a écrit :
Ok, I've mentioned the unit tests already... I've been fighting with
them all night with no luck (getting quite frustrated).
Fixed.
Jeff Jensen wrote:
Brett,
I am building from bootstrap. I think the latest PomWriter changes cause
this test to fail. Does it pass for you?
[exec] test:test:
[exec] [junit] Running org.apache.maven.artifact.PomRewriterTest
[exec] [junit] Tests run: 1, Failures: 0,
Yesterday there was a problem with mail.apache.org, it closed connections
before HELO. I noticed because I've just changed my server ISP and I was
knocking my head on the wall due to mail errors.
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Sunday, September
illez répondre à [EMAIL PROTECTED]
Pour : dev
cc :
Objet : Réf. : Re: Test failure when building head
Damn no, I was just trying to build it and not bootstrapping, now I'm
fighting against the proxy to bootstrap.
Extranet
[EMAIL PROTECTED] - 03/09/2004 13:12
Veuillez répondr
Damn no, I was just trying to build it and not bootstrapping, now I'm
fighting against the proxy to bootstrap.
Extranet
[EMAIL PROTECTED] - 03/09/2004 13:12
Veuillez répondre à [EMAIL PROTECTED]
Pour : dev
cc :
Objet : Re: Test failure when building head
Did you do a
Did you do a full bootstrap? This is a new test I added, and there is a
chance it could be using old data.
- Brett
[EMAIL PROTECTED] wrote:
Howdy
I just grabbed maven from cvs (head view), and when building I got a
[junit] [ERROR] TEST org.apache.maven.plugin.PluginManagerTest FAILED
here the tes
73 matches
Mail list logo
