Re: non-reproducible issues on CI
Hi Mark and I spent yesterday trying to figure out what is going on with this failing build. Here are our finding this far for maven-repository-plugin. 1. maven-invoker-plugin is used to install the current artifact (maven-repository-plugin) into a special repository used by the ITs, namely target/it-repo. The ITs are set up with their own repo so that the users local repository is not messed with. 2. maven-repository-collector-plugin is used to resolve the current artifact's (maven-repository-plugin) dependencies from the local repository to target/it-repo. 3. maven-surefire-plugin is used to run the ITs. When doing this it sets a system property maven.repo.local and points that to target/it-repo. When this is run with Maven 3.0.3 on the command line like this: mvn clean verify -Prun-its all is well and the ITs pass. When this is run with Maven 3.0.3 on the command line like this: mvn clean verify -Prun-its -Dmaven.repo.local=/local/repository the build fails because it cannot find maven-repository-plugin in the local repository. This is the way the CI builds are run, but it can be reproduced locally by adding the extra command line parameter. What seems to happening in that the -Dmaven.local.repository command line parameter overrides the system property set for the Surefire Plugin. Thus making maven-surefire-plugin look for maven-repository-plugin in the wrong repository (/local/repository). Does anyone have ideas how we can solve this? On 2011-07-30 01:22, Mark Struberg wrote: Hi! Our CI is broken since a while and most of the errors are of the following kind: [ERROR] Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT: Failure to find org.apache.maven.plugins:maven-repository-plugin:pom:2.3.2-SNAPSHOT in /home/hudson/hudson-slave/workspace/maven-plugins-ITs-3.x/maven-repository-plugin/target/it-repo was cached in the local repository, resolution will not be reattempted until the update interval of local.central has elapsed or updates are forced - [Help 1] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:129) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:261) at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:185) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:235) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:106) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:86) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:98) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:282) at
Re: non-reproducible issues on CI
Had a similar if not same issue while developing a plugin. Fixed it by
adding
systemProperties
localRepository${repository.integrationtests}localRepository
systemProperties
to surefire plugin configuration in IT phase.
Works for me with surefire-plugin 2.9 and invoker-plugin 1.5
Regards,
Ansgar
Am 31.07.2011 13:50 schrieb Dennis Lundberg denn...@apache.org:
Re: non-reproducible issues on CI
On 2011-07-31 14:42, Ansgar Konermann wrote:
Had a similar if not same issue while developing a plugin. Fixed it by
adding
systemProperties
localRepository${repository.integrationtests}localRepository
systemProperties
to surefire plugin configuration in IT phase.
Works for me with surefire-plugin 2.9 and invoker-plugin 1.5
Regards,
Ansgar
Am 31.07.2011 13:50 schrieb Dennis Lundberg denn...@apache.org:
Thanks for the hint. I have already tried this, but unfortunately it
doesn't work for this use case.
--
Dennis Lundberg
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: non-reproducible issues on CI
That's fine, but I fear only as long as you don't use -Dmaven.repo.local on
your commandline. And exactly that's how our jenkins was configured.
LieGrue,
strub
--- On Sun, 7/31/11, Ansgar Konermann ansgar.konerm...@googlemail.com wrote:
From: Ansgar Konermann ansgar.konerm...@googlemail.com
Subject: Re: non-reproducible issues on CI
To: Maven Developers List dev@maven.apache.org
Date: Sunday, July 31, 2011, 12:42 PM
Had a similar if not same issue while
developing a plugin. Fixed it by
adding
systemProperties
localRepository${repository.integrationtests}localRepository
systemProperties
to surefire plugin configuration in IT phase.
Works for me with surefire-plugin 2.9 and invoker-plugin
1.5
Regards,
Ansgar
Am 31.07.2011 13:50 schrieb Dennis Lundberg denn...@apache.org:
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: non-reproducible issues on CI
Mark,
THe problem is this: jenkins gets going using information from the
global settings.xml before any command-line args are processed. So
you've created a monster, as it were. Luckily, there's a job option to
use an alternative settings so long as it's in the svn real estate
that the job knows about. So while you can have infra deploy a
'special' maven, you don't have to.
--benson
On Sun, Jul 31, 2011 at 10:40 AM, Mark Struberg strub...@yahoo.de wrote:
That's fine, but I fear only as long as you don't use -Dmaven.repo.local on
your commandline. And exactly that's how our jenkins was configured.
LieGrue,
strub
--- On Sun, 7/31/11, Ansgar Konermann ansgar.konerm...@googlemail.com wrote:
From: Ansgar Konermann ansgar.konerm...@googlemail.com
Subject: Re: non-reproducible issues on CI
To: Maven Developers List dev@maven.apache.org
Date: Sunday, July 31, 2011, 12:42 PM
Had a similar if not same issue while
developing a plugin. Fixed it by
adding
systemProperties
localRepository${repository.integrationtests}localRepository
systemProperties
to surefire plugin configuration in IT phase.
Works for me with surefire-plugin 2.9 and invoker-plugin
1.5
Regards,
Ansgar
Am 31.07.2011 13:50 schrieb Dennis Lundberg denn...@apache.org:
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: non-reproducible issues on CI
Hi Benson!
Thanks for this information!
I don't have much clue about jenkins (apart from reading the build messages),
nor any detailed info about the setup at the ASF.
Did you understand Dennis' problem description and do have mojo + knowledge how
to fix this on our CI? Our problem is most probably that the current build uses
the -Dmaven.repo.local property to separate local repos for different builds.
I proposed to use a different maven installation just for being able to set the
localRepository. The settings option might as well do, at least worth a try.
Would be really appreciated and a big help if you could take the time and help
us fixing our CI build!
txs and LieGrue,
strub
--- On Sun, 7/31/11, Benson Margulies bimargul...@gmail.com wrote:
From: Benson Margulies bimargul...@gmail.com
Subject: Re: non-reproducible issues on CI
To: Maven Developers List dev@maven.apache.org
Date: Sunday, July 31, 2011, 2:49 PM
Mark,
THe problem is this: jenkins gets going using information
from the
global settings.xml before any command-line args are
processed. So
you've created a monster, as it were. Luckily, there's a
job option to
use an alternative settings so long as it's in the svn real
estate
that the job knows about. So while you can have infra
deploy a
'special' maven, you don't have to.
--benson
On Sun, Jul 31, 2011 at 10:40 AM, Mark Struberg strub...@yahoo.de
wrote:
That's fine, but I fear only as long as you don't use
-Dmaven.repo.local on your commandline. And exactly that's
how our jenkins was configured.
LieGrue,
strub
--- On Sun, 7/31/11, Ansgar Konermann ansgar.konerm...@googlemail.com
wrote:
From: Ansgar Konermann ansgar.konerm...@googlemail.com
Subject: Re: non-reproducible issues on CI
To: Maven Developers List dev@maven.apache.org
Date: Sunday, July 31, 2011, 12:42 PM
Had a similar if not same issue while
developing a plugin. Fixed it by
adding
systemProperties
localRepository${repository.integrationtests}localRepository
systemProperties
to surefire plugin configuration in IT phase.
Works for me with surefire-plugin 2.9 and
invoker-plugin
1.5
Regards,
Ansgar
Am 31.07.2011 13:50 schrieb Dennis Lundberg
denn...@apache.org:
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: non-reproducible issues on CI
If you check a settings.xml into the tree where this job can fetch it,
I will try to go from there.
On Sun, Jul 31, 2011 at 10:58 AM, Mark Struberg strub...@yahoo.de wrote:
Hi Benson!
Thanks for this information!
I don't have much clue about jenkins (apart from reading the build messages),
nor any detailed info about the setup at the ASF.
Did you understand Dennis' problem description and do have mojo + knowledge
how to fix this on our CI? Our problem is most probably that the current
build uses the -Dmaven.repo.local property to separate local repos for
different builds.
I proposed to use a different maven installation just for being able to set
the localRepository. The settings option might as well do, at least worth a
try.
Would be really appreciated and a big help if you could take the time and
help us fixing our CI build!
txs and LieGrue,
strub
--- On Sun, 7/31/11, Benson Margulies bimargul...@gmail.com wrote:
From: Benson Margulies bimargul...@gmail.com
Subject: Re: non-reproducible issues on CI
To: Maven Developers List dev@maven.apache.org
Date: Sunday, July 31, 2011, 2:49 PM
Mark,
THe problem is this: jenkins gets going using information
from the
global settings.xml before any command-line args are
processed. So
you've created a monster, as it were. Luckily, there's a
job option to
use an alternative settings so long as it's in the svn real
estate
that the job knows about. So while you can have infra
deploy a
'special' maven, you don't have to.
--benson
On Sun, Jul 31, 2011 at 10:40 AM, Mark Struberg strub...@yahoo.de
wrote:
That's fine, but I fear only as long as you don't use
-Dmaven.repo.local on your commandline. And exactly that's
how our jenkins was configured.
LieGrue,
strub
--- On Sun, 7/31/11, Ansgar Konermann ansgar.konerm...@googlemail.com
wrote:
From: Ansgar Konermann ansgar.konerm...@googlemail.com
Subject: Re: non-reproducible issues on CI
To: Maven Developers List dev@maven.apache.org
Date: Sunday, July 31, 2011, 12:42 PM
Had a similar if not same issue while
developing a plugin. Fixed it by
adding
systemProperties
localRepository${repository.integrationtests}localRepository
systemProperties
to surefire plugin configuration in IT phase.
Works for me with surefire-plugin 2.9 and
invoker-plugin
1.5
Regards,
Ansgar
Am 31.07.2011 13:50 schrieb Dennis Lundberg
denn...@apache.org:
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: non-reproducible issues on CI
I will re-expose the Sonatype Hudson instances as a point of reference. They
have been running successfully since you guys flipped over to Jenkins. Our
setup can at least serve as some guidance as to what might be wrong with your
setup.
On Jul 31, 2011, at 10:58 AM, Mark Struberg wrote:
Hi Benson!
Thanks for this information!
I don't have much clue about jenkins (apart from reading the build messages),
nor any detailed info about the setup at the ASF.
Did you understand Dennis' problem description and do have mojo + knowledge
how to fix this on our CI? Our problem is most probably that the current
build uses the -Dmaven.repo.local property to separate local repos for
different builds.
I proposed to use a different maven installation just for being able to set
the localRepository. The settings option might as well do, at least worth a
try.
Would be really appreciated and a big help if you could take the time and
help us fixing our CI build!
txs and LieGrue,
strub
--- On Sun, 7/31/11, Benson Margulies bimargul...@gmail.com wrote:
From: Benson Margulies bimargul...@gmail.com
Subject: Re: non-reproducible issues on CI
To: Maven Developers List dev@maven.apache.org
Date: Sunday, July 31, 2011, 2:49 PM
Mark,
THe problem is this: jenkins gets going using information
from the
global settings.xml before any command-line args are
processed. So
you've created a monster, as it were. Luckily, there's a
job option to
use an alternative settings so long as it's in the svn real
estate
that the job knows about. So while you can have infra
deploy a
'special' maven, you don't have to.
--benson
On Sun, Jul 31, 2011 at 10:40 AM, Mark Struberg strub...@yahoo.de
wrote:
That's fine, but I fear only as long as you don't use
-Dmaven.repo.local on your commandline. And exactly that's
how our jenkins was configured.
LieGrue,
strub
--- On Sun, 7/31/11, Ansgar Konermann ansgar.konerm...@googlemail.com
wrote:
From: Ansgar Konermann ansgar.konerm...@googlemail.com
Subject: Re: non-reproducible issues on CI
To: Maven Developers List dev@maven.apache.org
Date: Sunday, July 31, 2011, 12:42 PM
Had a similar if not same issue while
developing a plugin. Fixed it by
adding
systemProperties
localRepository${repository.integrationtests}localRepository
systemProperties
to surefire plugin configuration in IT phase.
Works for me with surefire-plugin 2.9 and
invoker-plugin
1.5
Regards,
Ansgar
Am 31.07.2011 13:50 schrieb Dennis Lundberg
denn...@apache.org:
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
-
First, the taking in of scattered particulars under one Idea,
so that everyone understands what is being talked about ... Second,
the separation of the Idea into parts, by dividing it at the joints,
as nature directs, not breaking any limb in half as a bad carver might.
-- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
Re: non-reproducible issues on CI
Hi Jason!
The bugs are fixed already. What we now see are _real_ bugs and they should
fail in your CI system too (can also be reproduced locally).
LieGrue,
strub
--- On Sun, 7/31/11, Jason van Zyl ja...@sonatype.com wrote:
From: Jason van Zyl ja...@sonatype.com
Subject: Re: non-reproducible issues on CI
To: Maven Developers List dev@maven.apache.org
Date: Sunday, July 31, 2011, 8:41 PM
I will re-expose the Sonatype Hudson
instances as a point of reference. They have been running
successfully since you guys flipped over to Jenkins. Our
setup can at least serve as some guidance as to what might
be wrong with your setup.
On Jul 31, 2011, at 10:58 AM, Mark Struberg wrote:
Hi Benson!
Thanks for this information!
I don't have much clue about jenkins (apart from
reading the build messages), nor any detailed info about the
setup at the ASF.
Did you understand Dennis' problem description and do
have mojo + knowledge how to fix this on our CI? Our problem
is most probably that the current build uses the
-Dmaven.repo.local property to separate local repos for
different builds.
I proposed to use a different maven installation just
for being able to set the localRepository. The settings
option might as well do, at least worth a try.
Would be really appreciated and a big help if you
could take the time and help us fixing our CI build!
txs and LieGrue,
strub
--- On Sun, 7/31/11, Benson Margulies bimargul...@gmail.com
wrote:
From: Benson Margulies bimargul...@gmail.com
Subject: Re: non-reproducible issues on CI
To: Maven Developers List dev@maven.apache.org
Date: Sunday, July 31, 2011, 2:49 PM
Mark,
THe problem is this: jenkins gets going using
information
from the
global settings.xml before any command-line args
are
processed. So
you've created a monster, as it were. Luckily,
there's a
job option to
use an alternative settings so long as it's in the
svn real
estate
that the job knows about. So while you can have
infra
deploy a
'special' maven, you don't have to.
--benson
On Sun, Jul 31, 2011 at 10:40 AM, Mark Struberg
strub...@yahoo.de
wrote:
That's fine, but I fear only as long as you
don't use
-Dmaven.repo.local on your commandline. And
exactly that's
how our jenkins was configured.
LieGrue,
strub
--- On Sun, 7/31/11, Ansgar Konermann ansgar.konerm...@googlemail.com
wrote:
From: Ansgar Konermann ansgar.konerm...@googlemail.com
Subject: Re: non-reproducible issues on
CI
To: Maven Developers List dev@maven.apache.org
Date: Sunday, July 31, 2011, 12:42 PM
Had a similar if not same issue while
developing a plugin. Fixed it by
adding
systemProperties
localRepository${repository.integrationtests}localRepository
systemProperties
to surefire plugin configuration in IT
phase.
Works for me with surefire-plugin 2.9 and
invoker-plugin
1.5
Regards,
Ansgar
Am 31.07.2011 13:50 schrieb Dennis
Lundberg
denn...@apache.org:
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
-
First, the taking in of scattered particulars under one
Idea,
so that everyone understands what is being talked about ...
Second,
the separation of the Idea into parts, by dividing it at
the joints,
as nature directs, not breaking any limb in half as a bad
carver might.
-- Plato, Phaedrus (Notes on the Synthesis of Form
by C. Alexander)
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: non-reproducible issues on CI
It turns out that someone had accidently arranged for several projects
to share a workspace, and then to use a private maven repo inside that
workspace, with the predicable disasterous consequences.
However, I'm sure the Sonatype config will be helpful.
On Sun, Jul 31, 2011 at 4:41 PM, Jason van Zyl ja...@sonatype.com wrote:
I will re-expose the Sonatype Hudson instances as a point of reference. They
have been running successfully since you guys flipped over to Jenkins. Our
setup can at least serve as some guidance as to what might be wrong with your
setup.
On Jul 31, 2011, at 10:58 AM, Mark Struberg wrote:
Hi Benson!
Thanks for this information!
I don't have much clue about jenkins (apart from reading the build
messages), nor any detailed info about the setup at the ASF.
Did you understand Dennis' problem description and do have mojo + knowledge
how to fix this on our CI? Our problem is most probably that the current
build uses the -Dmaven.repo.local property to separate local repos for
different builds.
I proposed to use a different maven installation just for being able to set
the localRepository. The settings option might as well do, at least worth a
try.
Would be really appreciated and a big help if you could take the time and
help us fixing our CI build!
txs and LieGrue,
strub
--- On Sun, 7/31/11, Benson Margulies bimargul...@gmail.com wrote:
From: Benson Margulies bimargul...@gmail.com
Subject: Re: non-reproducible issues on CI
To: Maven Developers List dev@maven.apache.org
Date: Sunday, July 31, 2011, 2:49 PM
Mark,
THe problem is this: jenkins gets going using information
from the
global settings.xml before any command-line args are
processed. So
you've created a monster, as it were. Luckily, there's a
job option to
use an alternative settings so long as it's in the svn real
estate
that the job knows about. So while you can have infra
deploy a
'special' maven, you don't have to.
--benson
On Sun, Jul 31, 2011 at 10:40 AM, Mark Struberg strub...@yahoo.de
wrote:
That's fine, but I fear only as long as you don't use
-Dmaven.repo.local on your commandline. And exactly that's
how our jenkins was configured.
LieGrue,
strub
--- On Sun, 7/31/11, Ansgar Konermann ansgar.konerm...@googlemail.com
wrote:
From: Ansgar Konermann ansgar.konerm...@googlemail.com
Subject: Re: non-reproducible issues on CI
To: Maven Developers List dev@maven.apache.org
Date: Sunday, July 31, 2011, 12:42 PM
Had a similar if not same issue while
developing a plugin. Fixed it by
adding
systemProperties
localRepository${repository.integrationtests}localRepository
systemProperties
to surefire plugin configuration in IT phase.
Works for me with surefire-plugin 2.9 and
invoker-plugin
1.5
Regards,
Ansgar
Am 31.07.2011 13:50 schrieb Dennis Lundberg
denn...@apache.org:
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
-
First, the taking in of scattered particulars under one Idea,
so that everyone understands what is being talked about ... Second,
the separation of the Idea into parts, by dividing it at the joints,
as nature directs, not breaking any limb in half as a bad carver might.
-- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
RE: non-reproducible issues on CI
Hi Martin! Good idea basically. But nope, both snapshots and releases are set to true. LieGrue, strub --- On Sat, 7/30/11, Martin Gainty mgai...@hotmail.com wrote: From: Martin Gainty mgai...@hotmail.com Subject: RE: non-reproducible issues on CI To: dev@maven.apache.org Date: Saturday, July 30, 2011, 2:02 AM Mark- ..do you have snapshots enabled false for your repository..e.g repositories repository snapshots enabledfalse/enabled /snapshots /repository /repositories Liebe GruBe Martin Date: Sat, 30 Jul 2011 00:22:12 +0100 From: strub...@yahoo.de Subject: non-reproducible issues on CI To: dev@maven.apache.org Hi! Our CI is broken since a while and most of the errors are of the following kind: [ERROR] Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT: Failure to find org.apache.maven.plugins:maven-repository-plugin:pom:2.3.2-SNAPSHOT in /home/hudson/hudson-slave/workspace/maven-plugins-ITs-3.x/maven-repository-plugin/target/it-repo was cached in the local repository, resolution will not be reattempted until the update interval of local.central has elapsed or updates are forced - [Help 1] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:129) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:261) at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:185) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:235) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:106) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:86) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:98) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:282) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:172) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:316) at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:115) ... 20 more Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Failure to find org.apache.maven.plugins:maven-repository-plugin:pom:2.3.2-SNAPSHOT in /home/hudson/hudson-slave/workspace/maven-plugins-ITs-3.x/maven-repository-plugin/target/it-repo was cached in the local repository, resolution will not be reattempted until the update interval of local.central has elapsed or updates are forced at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:541
Re: non-reproducible issues on CI
Hi I've seen this kind of error at my day job a couple of times. Although I'm sure sure why they happen, I do know how to get rid of it. You need to manually remove the offending artifact from the local repo to get a freshly downloaded copy of it. By removing all versions of the artifact, including the meta data you ensure that the corrupt meta data will also be removed. The only reason I can think of as to why it happens is that the repository don't respond when the artifact is being downloaded for the first time. That puts some special meta data in the local repository. That meta data looks like it is supposed to help determine when the failed attempt occurred. This somehow blocks any further download of the artifact in question. Even forcing a new download via command line option have failed for us. I haven't reported it in JIRA yet because I don't have anything even remotely reproducible. On 2011-07-30 01:22, Mark Struberg wrote: Hi! Our CI is broken since a while and most of the errors are of the following kind: [ERROR] Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT: Failure to find org.apache.maven.plugins:maven-repository-plugin:pom:2.3.2-SNAPSHOT in /home/hudson/hudson-slave/workspace/maven-plugins-ITs-3.x/maven-repository-plugin/target/it-repo was cached in the local repository, resolution will not be reattempted until the update interval of local.central has elapsed or updates are forced - [Help 1] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:129) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:261) at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:185) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:235) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:106) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:86) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:98) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:282) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:172) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:316) at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:115) ... 20 more Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Failure to find org.apache.maven.plugins:maven-repository-plugin:pom:2.3.2-SNAPSHOT in /home/hudson/hudson-slave/workspace/maven-plugins-ITs-3.x/maven-repository-plugin/target/it-repo was
Re: non-reproducible issues on CI
Might be if the metadata got downloaded but the artifact (a fat jar for example) didn't make it? I bet there are situations where such things still might end ugly. Just for the record: I'm currently looking at maven-repository-plugin BundleCreateIT#createWithSCMInfoProvided(). It looks like this issue only hits ITs. Here is the local IT repo on our CI box: https://builds.apache.org/job/maven-plugins-ITs-3.x/ws/maven-repository-plugin/target/it-repo/ A comparison of the artifacts I get locally shows that commons-cli-1.0 and commons-lang-2.1 don't make it on the CI box. I'll try to ping infra and get drop them from our jenkins repo cache. LieGrue, strub --- On Sat, 7/30/11, Dennis Lundberg denn...@apache.org wrote: From: Dennis Lundberg denn...@apache.org Subject: Re: non-reproducible issues on CI To: Maven Developers List dev@maven.apache.org Date: Saturday, July 30, 2011, 8:31 AM Hi I've seen this kind of error at my day job a couple of times. Although I'm sure sure why they happen, I do know how to get rid of it. You need to manually remove the offending artifact from the local repo to get a freshly downloaded copy of it. By removing all versions of the artifact, including the meta data you ensure that the corrupt meta data will also be removed. The only reason I can think of as to why it happens is that the repository don't respond when the artifact is being downloaded for the first time. That puts some special meta data in the local repository. That meta data looks like it is supposed to help determine when the failed attempt occurred. This somehow blocks any further download of the artifact in question. Even forcing a new download via command line option have failed for us. I haven't reported it in JIRA yet because I don't have anything even remotely reproducible. On 2011-07-30 01:22, Mark Struberg wrote: Hi! Our CI is broken since a while and most of the errors are of the following kind: [ERROR] Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT: Failure to find org.apache.maven.plugins:maven-repository-plugin:pom:2.3.2-SNAPSHOT in /home/hudson/hudson-slave/workspace/maven-plugins-ITs-3.x/maven-repository-plugin/target/it-repo was cached in the local repository, resolution will not be reattempted until the update interval of local.central has elapsed or updates are forced - [Help 1] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:129) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:261) at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:185) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:235) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:106) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:86) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:98) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to read
Re: non-reproducible issues on CI
I replied to the other thread saying it sounded similar to MNG-5084 [1] - if that sounds like it to you add your votes to the ticket. [1] http://jira.codehaus.org/browse/MNG-5084 On 30/07/2011, at 8:31 PM, Dennis Lundberg wrote: I haven't reported it in JIRA yet because I don't have anything even remotely reproducible.
Re: non-reproducible issues on CI
Hi! I'll try to reproduce it on the weekend. LieGrue, strub --- On Sat, 7/30/11, Mark Derricutt m...@talios.com wrote: From: Mark Derricutt m...@talios.com Subject: Re: non-reproducible issues on CI To: Maven Developers List dev@maven.apache.org Date: Saturday, July 30, 2011, 8:54 AM I replied to the other thread saying it sounded similar to MNG-5084 [1] - if that sounds like it to you add your votes to the ticket. [1] http://jira.codehaus.org/browse/MNG-5084 On 30/07/2011, at 8:31 PM, Dennis Lundberg wrote: I haven't reported it in JIRA yet because I don't have anything even remotely reproducible. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: non-reproducible issues on CI
On 2011-07-30 10:54, Mark Struberg wrote: Might be if the metadata got downloaded but the artifact (a fat jar for example) didn't make it? I bet there are situations where such things still might end ugly. Just for the record: I'm currently looking at maven-repository-plugin BundleCreateIT#createWithSCMInfoProvided(). It looks like this issue only hits ITs. Here is the local IT repo on our CI box: https://builds.apache.org/job/maven-plugins-ITs-3.x/ws/maven-repository-plugin/target/it-repo/ A comparison of the artifacts I get locally shows that commons-cli-1.0 and commons-lang-2.1 don't make it on the CI box. I'll try to ping infra and get drop them from our jenkins repo cache. That should be directed to builds@a.o I'm a recent subscriber there, so I can ask them. LieGrue, strub --- On Sat, 7/30/11, Dennis Lundberg denn...@apache.org wrote: From: Dennis Lundberg denn...@apache.org Subject: Re: non-reproducible issues on CI To: Maven Developers List dev@maven.apache.org Date: Saturday, July 30, 2011, 8:31 AM Hi I've seen this kind of error at my day job a couple of times. Although I'm sure sure why they happen, I do know how to get rid of it. You need to manually remove the offending artifact from the local repo to get a freshly downloaded copy of it. By removing all versions of the artifact, including the meta data you ensure that the corrupt meta data will also be removed. The only reason I can think of as to why it happens is that the repository don't respond when the artifact is being downloaded for the first time. That puts some special meta data in the local repository. That meta data looks like it is supposed to help determine when the failed attempt occurred. This somehow blocks any further download of the artifact in question. Even forcing a new download via command line option have failed for us. I haven't reported it in JIRA yet because I don't have anything even remotely reproducible. On 2011-07-30 01:22, Mark Struberg wrote: Hi! Our CI is broken since a while and most of the errors are of the following kind: [ERROR] Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT: Failure to find org.apache.maven.plugins:maven-repository-plugin:pom:2.3.2-SNAPSHOT in /home/hudson/hudson-slave/workspace/maven-plugins-ITs-3.x/maven-repository-plugin/target/it-repo was cached in the local repository, resolution will not be reattempted until the update interval of local.central has elapsed or updates are forced - [Help 1] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:129) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:261) at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:185) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:235) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:106) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:86) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:98) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409
Re: non-reproducible issues on CI
gav dropped it already (pinged him on IRC). Build #152 is currently running. LieGrue, strub --- On Sat, 7/30/11, Dennis Lundberg denn...@apache.org wrote: From: Dennis Lundberg denn...@apache.org Subject: Re: non-reproducible issues on CI To: Maven Developers List dev@maven.apache.org Date: Saturday, July 30, 2011, 9:55 AM On 2011-07-30 10:54, Mark Struberg wrote: Might be if the metadata got downloaded but the artifact (a fat jar for example) didn't make it? I bet there are situations where such things still might end ugly. Just for the record: I'm currently looking at maven-repository-plugin BundleCreateIT#createWithSCMInfoProvided(). It looks like this issue only hits ITs. Here is the local IT repo on our CI box: https://builds.apache.org/job/maven-plugins-ITs-3.x/ws/maven-repository-plugin/target/it-repo/ A comparison of the artifacts I get locally shows that commons-cli-1.0 and commons-lang-2.1 don't make it on the CI box. I'll try to ping infra and get drop them from our jenkins repo cache. That should be directed to builds@a.o I'm a recent subscriber there, so I can ask them. LieGrue, strub --- On Sat, 7/30/11, Dennis Lundberg denn...@apache.org wrote: From: Dennis Lundberg denn...@apache.org Subject: Re: non-reproducible issues on CI To: Maven Developers List dev@maven.apache.org Date: Saturday, July 30, 2011, 8:31 AM Hi I've seen this kind of error at my day job a couple of times. Although I'm sure sure why they happen, I do know how to get rid of it. You need to manually remove the offending artifact from the local repo to get a freshly downloaded copy of it. By removing all versions of the artifact, including the meta data you ensure that the corrupt meta data will also be removed. The only reason I can think of as to why it happens is that the repository don't respond when the artifact is being downloaded for the first time. That puts some special meta data in the local repository. That meta data looks like it is supposed to help determine when the failed attempt occurred. This somehow blocks any further download of the artifact in question. Even forcing a new download via command line option have failed for us. I haven't reported it in JIRA yet because I don't have anything even remotely reproducible. On 2011-07-30 01:22, Mark Struberg wrote: Hi! Our CI is broken since a while and most of the errors are of the following kind: [ERROR] Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT: Failure to find org.apache.maven.plugins:maven-repository-plugin:pom:2.3.2-SNAPSHOT in /home/hudson/hudson-slave/workspace/maven-plugins-ITs-3.x/maven-repository-plugin/target/it-repo was cached in the local repository, resolution will not be reattempted until the update interval of local.central has elapsed or updates are forced - [Help 1] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:129) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:261) at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:185) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:235) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:106) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:86) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:98) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke
Re: non-reproducible issues on CI
These jobs should use a custom repo. Trusting the built-in Jenkins repo is not wise when testing maven. It's just a checkbox in the job config. On Sat, Jul 30, 2011 at 6:09 AM, Mark Struberg strub...@yahoo.de wrote: gav dropped it already (pinged him on IRC). Build #152 is currently running. LieGrue, strub --- On Sat, 7/30/11, Dennis Lundberg denn...@apache.org wrote: From: Dennis Lundberg denn...@apache.org Subject: Re: non-reproducible issues on CI To: Maven Developers List dev@maven.apache.org Date: Saturday, July 30, 2011, 9:55 AM On 2011-07-30 10:54, Mark Struberg wrote: Might be if the metadata got downloaded but the artifact (a fat jar for example) didn't make it? I bet there are situations where such things still might end ugly. Just for the record: I'm currently looking at maven-repository-plugin BundleCreateIT#createWithSCMInfoProvided(). It looks like this issue only hits ITs. Here is the local IT repo on our CI box: https://builds.apache.org/job/maven-plugins-ITs-3.x/ws/maven-repository-plugin/target/it-repo/ A comparison of the artifacts I get locally shows that commons-cli-1.0 and commons-lang-2.1 don't make it on the CI box. I'll try to ping infra and get drop them from our jenkins repo cache. That should be directed to builds@a.o I'm a recent subscriber there, so I can ask them. LieGrue, strub --- On Sat, 7/30/11, Dennis Lundberg denn...@apache.org wrote: From: Dennis Lundberg denn...@apache.org Subject: Re: non-reproducible issues on CI To: Maven Developers List dev@maven.apache.org Date: Saturday, July 30, 2011, 8:31 AM Hi I've seen this kind of error at my day job a couple of times. Although I'm sure sure why they happen, I do know how to get rid of it. You need to manually remove the offending artifact from the local repo to get a freshly downloaded copy of it. By removing all versions of the artifact, including the meta data you ensure that the corrupt meta data will also be removed. The only reason I can think of as to why it happens is that the repository don't respond when the artifact is being downloaded for the first time. That puts some special meta data in the local repository. That meta data looks like it is supposed to help determine when the failed attempt occurred. This somehow blocks any further download of the artifact in question. Even forcing a new download via command line option have failed for us. I haven't reported it in JIRA yet because I don't have anything even remotely reproducible. On 2011-07-30 01:22, Mark Struberg wrote: Hi! Our CI is broken since a while and most of the errors are of the following kind: [ERROR] Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT: Failure to find org.apache.maven.plugins:maven-repository-plugin:pom:2.3.2-SNAPSHOT in /home/hudson/hudson-slave/workspace/maven-plugins-ITs-3.x/maven-repository-plugin/target/it-repo was cached in the local repository, resolution will not be reattempted until the update interval of local.central has elapsed or updates are forced - [Help 1] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:129) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:261) at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:185) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:235) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:106) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:86) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:98) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196
RE: non-reproducible issues on CI
Mark- ..do you have snapshots enabled false for your repository..e.g repositories repository snapshots enabledfalse/enabled /snapshots /repository /repositories Liebe GruBe Martin __ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Date: Sat, 30 Jul 2011 00:22:12 +0100 From: strub...@yahoo.de Subject: non-reproducible issues on CI To: dev@maven.apache.org Hi! Our CI is broken since a while and most of the errors are of the following kind: [ERROR] Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT: Failure to find org.apache.maven.plugins:maven-repository-plugin:pom:2.3.2-SNAPSHOT in /home/hudson/hudson-slave/workspace/maven-plugins-ITs-3.x/maven-repository-plugin/target/it-repo was cached in the local repository, resolution will not be reattempted until the update interval of local.central has elapsed or updates are forced - [Help 1] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:129) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:261) at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:185) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:235) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:106) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:86) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:98) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:282) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:172) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:316) at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:115) ... 20 more Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Failure to find org.apache.maven.plugins:maven-repository-plugin:pom:2.3.2-SNAPSHOT in /home/hudson/hudson-slave/workspace/maven-plugins-ITs-3.x/maven-repository-plugin/target/it-repo was cached in the local repository, resolution will not be reattempted until the update interval of local.central has
Re: non-reproducible issues on CI
I think I've seen a similar error come up on a few boxes of my own. I think it has something to do with the lastUpdated terminator in your repository. I've had some success removing this off of POMs that wouldn't download. Alternatively, nuking the repository might help. My two cents. Andrew On Jul 29, 2011, at 6:22 PM, Mark Struberg wrote: Hi! Our CI is broken since a while and most of the errors are of the following kind: [ERROR] Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT: Failure to find org.apache.maven.plugins:maven-repository-plugin:pom:2.3.2-SNAPSHOT in /home/hudson/hudson-slave/workspace/maven-plugins-ITs-3.x/maven-repository-plugin/target/it-repo was cached in the local repository, resolution will not be reattempted until the update interval of local.central has elapsed or updates are forced - [Help 1] org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-repository-plugin:2.3.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:129) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:261) at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:185) at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:235) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:106) at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:86) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:98) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-repository-plugin:jar:2.3.2-SNAPSHOT at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:282) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:172) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:316) at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:115) ... 20 more Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Failure to find org.apache.maven.plugins:maven-repository-plugin:pom:2.3.2-SNAPSHOT in /home/hudson/hudson-slave/workspace/maven-plugins-ITs-3.x/maven-repository-plugin/target/it-repo was cached in the local repository, resolution will not be reattempted until the update interval of local.central has elapsed or updates are forced at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:541) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:220) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:197) at
