RE: Maven's snapshot mechanism is horked (Re: Build error - Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/project-config/pom.xml?)
Hi Jason, download of SNAPSHOT dependencies does not work at all in M2.0.4: http://jira.codehaus.org/browse/MNG-1908 - Jörg Jason Dillon wrote on Saturday, October 14, 2006 10:17 PM: On Oct 14, 2006, at 6:58 AM, Kenney Westerhof wrote: Running mvn with -U -cpu should fix that (or wait 24 hours and try again :)). I don't think this helps... at least not the wait 24 hours. I was up late and was running a build at 11:50pm and it ran fine, then ran a build at 12:02am and it puked about missing versions from genesis 1.1- SNAPSHOT versions... which I had versions in my local repo that were all newer than any snap that I had deployed and I am the only one who deploys them, so no chance that it as deployed by someone else. The only way I could fix was to build genesis locally after the failed 12:02am build. But the crazy part was that I had just done that at about 11:40pm, did *not deploy* so my local copy was newer, but maven decided not to resolve to those versions?!?! I don't think using `mvn -U` helps either, as that negates the use of caching SNAPSHOTs and will slowdown the build way to much. Another solution is to delete the metadata file from the local repository. Nope... this does not work either as the problem shows up quite often when you removed you local repo and build... ie... no local metadata at all. So I don't think the problem is there. If there is a problem with the local metadata it is getting corrupted while mvn is running, so even removing the local repo cache will not ensure that the run will succeed. Btw, how come the original snapshot versions are removed from the remote repository? The local metadata file probably contains a reference to the old snapshot version, but doesn't seem to have it locally, which needs investigation.. Who said anything about removing anything? The genesis 1.1-SNAPSHOTS have not been altered ore removed from the remote repo. In the specific problem build 1 - 23 of plugin-support are all available. As for the other snapshot errors: Maven 1 legacy repositories don't contain metadata files. Updating snapshots from them doesn't seem to work. That's another thing that should be investigated. I personally never have problems with snapshot versions, so maybe the use of maven 1 repositories and the removal of snapshots from the remote repository isn't handled correctly by Maven. I know there are issues with m1 repos... not specific to snapshots... though unfortunately we can not eliminate them completely from out build because we have a few dependencies which define m1 repos in their poms. But... I think that use of m1 repos is only one of the problems going on here... something else, which I have yet to understand, is broken. One thing does look very fishy to me though snip 1) org.apache.geronimo.genesis.plugins:plugin-support:jar:1.1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file - DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=plugin- support \ -Dversion=1.1-20061013.014841-21 -Dpackaging=jar -Dfile=/ path/to/file Path to dependency: 1) org.apache.geronimo.genesis.plugins:tools-maven- plugin:maven-plugin:1.1-20061013.014841-21 2) org.apache.geronimo.genesis.plugins:plugin-support:jar: 1.1-20061013.014841-21 -- 1 required artifact is missing. for artifact: org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-plugin: 1.1-20061013.014841-21 from the specified /snip Notice that the tools-maven-plugin's timestamp-build is 20061013.014841-21 and this is also the same timestamp-build that is being used for the plugin-support jar. However the real timestamp for build 21 of plugins-support is 20061012.062745. --jason - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven's snapshot mechanism is horked (Re: Build error - Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/project-config/pom.xml?)
I think I have tracked this down... looks like ${pom.version} is
getting resolved to a timestamp version instead of the value it its
parents version element.
Is this expected?
If my parent has 1.1-SNAPSHOT, and an intermediate module defines a
dependency using ${pom.version}, should this resolve to 1.1-SNAPSHOT
or to 1.1-timestamp-build for the current module?
--jason
On Oct 14, 2006, at 6:58 AM, Kenney Westerhof wrote:
The problem below seems to indicate that the local repository
contains an old metadata file.
Running mvn with -U -cpu should fix that (or wait 24 hours and try
again :)).
Another solution is to delete the metadata file from the local
repository.
Btw, how come the original snapshot versions are removed from the
remote repository?
The local metadata file probably contains a reference to the old
snapshot version,
but doesn't seem to have it locally, which needs investigation..
As for the other snapshot errors: Maven 1 legacy repositories don't
contain metadata files. Updating snapshots from them doesn't seem
to work. That's another thing that
should be investigated.
I personally never have problems with snapshot versions, so maybe
the use of maven 1 repositories
and the removal of snapshots from the remote repository isn't
handled correctly by Maven.
-- Kenney
Jason Dillon wrote:
Folks... maven's handling of *SNAPSHOT artifacts is killing us.
Any idea what is going on... and how we can fix this. Its an
ongoing problem, seems like new timestamp mismatch problems are
popping up quite often now. I've already removed our direct use
of m1 repos to get around some problems resolving artifacts... but
something is still very broken with maven's SNAPSHOT mechanism.
Any ideas?
--jason
Begin forwarded message:
From: Jason Dillon [EMAIL PROTECTED]
Date: October 13, 2006 2:00:50 PM PDT
To: dev@geronimo.apache.org
Cc: Jason van Zyl [EMAIL PROTECTED]
Subject: Maven's snapshot mechanism is horked (Re: Build error -
Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/
project-config/pom.xml?)
Yes, build genesis locally for now to get around... I'm gonna
need to get the maven peeps to explain wtf is going on... and
hopefully fix maven to not freak out like this.
The metadata for plugin-support is correct... showing the latest
1.1-SNAPSHOT is -23:
metadata
groupIdorg.apache.geronimo.genesis.plugins/groupId
artifactIdplugin-support/artifactId
version1.1-SNAPSHOT/version
versioning
snapshot
timestamp20061013.014841/timestamp
buildNumber23/buildNumber
/snapshot
lastUpdated20061013014947/lastUpdated
/versioning
/metadata
And -23 is there:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/
geronimo/genesis/plugins/plugin-support/1.1-SNAPSHOT/plugin-
support-1.1-20061013.014841-23.jar
http://people.apache.org/repo/m2-snapshot-repository/org/apache/
geronimo/genesis/plugins/plugin-support/1.1-SNAPSHOT/plugin-
support-1.1-20061013.014841-23.pom
So, Maven *should* be resolving any 1.1-SNAPSHOT of plugin-config
to these files... but...
--jason
On Oct 13, 2006, at 1:50 PM, Joe Bohn wrote:
Prasad and I hit the same problem earlier today. There must be
something strange going on with the version # where 21 is
being assumed instead of the 23 that is actually in the repo.
I'm hoping that Jason will know what exactly is going on and how
to fix it and I suspect it may be related to one of his changes.
To get around the problem for now you can build genesis
locally. That worked for me.
Joe
Donald Woods wrote:
Having build problems today and wondering if the below genesis
change yesterday is causing it?
Started with a new trunk checkout directory on a SLES10 x86
machine.
Removed the existing .m2 repo.
bootstrap clean ran fine.
bootstrap specs is failing (also tried mvn -U install from
target/external/specs) because the file
version=1.1-20061013.014841-21 is not in the snapshot repo, but
version=1.1-20061013.014841-23 is.
--
--
[ERROR] BUILD ERROR
[INFO]
--
--
[INFO] Failed to resolve artifact.
Missing:
--
1) org.apache.geronimo.genesis.plugins:plugin-support:jar:1.1-
SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -
DgroupId=org.apache.geronimo.genesis.plugins -
DartifactId=plugin-support \
-Dversion=1.1-20061013.014841-21 -Dpackaging=jar -
Dfile=/path/to/file
Path to dependency:
1) org.apache.geronimo.genesis.plugins:tools-maven-
plugin:maven-plugin:1.1-20061013.014841-21 2)
org.apache.geronimo.genesis.plugins:plugin-support:jar:
1.1-20061013.014841-21 --
1 required artifact is missing.
for artifact:
org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven
Re: Maven's snapshot mechanism is horked (Re: Build error - Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/project-config/pom.xml?)
On Oct 14, 2006, at 6:58 AM, Kenney Westerhof wrote: Running mvn with -U -cpu should fix that (or wait 24 hours and try again :)). I don't think this helps... at least not the wait 24 hours. I was up late and was running a build at 11:50pm and it ran fine, then ran a build at 12:02am and it puked about missing versions from genesis 1.1- SNAPSHOT versions... which I had versions in my local repo that were all newer than any snap that I had deployed and I am the only one who deploys them, so no chance that it as deployed by someone else. The only way I could fix was to build genesis locally after the failed 12:02am build. But the crazy part was that I had just done that at about 11:40pm, did *not deploy* so my local copy was newer, but maven decided not to resolve to those versions?!?! I don't think using `mvn -U` helps either, as that negates the use of caching SNAPSHOTs and will slowdown the build way to much. Another solution is to delete the metadata file from the local repository. Nope... this does not work either as the problem shows up quite often when you removed you local repo and build... ie... no local metadata at all. So I don't think the problem is there. If there is a problem with the local metadata it is getting corrupted while mvn is running, so even removing the local repo cache will not ensure that the run will succeed. Btw, how come the original snapshot versions are removed from the remote repository? The local metadata file probably contains a reference to the old snapshot version, but doesn't seem to have it locally, which needs investigation.. Who said anything about removing anything? The genesis 1.1-SNAPSHOTS have not been altered ore removed from the remote repo. In the specific problem build 1 - 23 of plugin-support are all available. As for the other snapshot errors: Maven 1 legacy repositories don't contain metadata files. Updating snapshots from them doesn't seem to work. That's another thing that should be investigated. I personally never have problems with snapshot versions, so maybe the use of maven 1 repositories and the removal of snapshots from the remote repository isn't handled correctly by Maven. I know there are issues with m1 repos... not specific to snapshots... though unfortunately we can not eliminate them completely from out build because we have a few dependencies which define m1 repos in their poms. But... I think that use of m1 repos is only one of the problems going on here... something else, which I have yet to understand, is broken. One thing does look very fishy to me though snip 1) org.apache.geronimo.genesis.plugins:plugin-support:jar:1.1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file - DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=plugin- support \ -Dversion=1.1-20061013.014841-21 -Dpackaging=jar -Dfile=/ path/to/file Path to dependency: 1) org.apache.geronimo.genesis.plugins:tools-maven- plugin:maven-plugin:1.1-20061013.014841-21 2) org.apache.geronimo.genesis.plugins:plugin-support:jar: 1.1-20061013.014841-21 -- 1 required artifact is missing. for artifact: org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-plugin: 1.1-20061013.014841-21 from the specified /snip Notice that the tools-maven-plugin's timestamp-build is 20061013.014841-21 and this is also the same timestamp-build that is being used for the plugin-support jar. However the real timestamp for build 21 of plugins-support is 20061012.062745. --jason
