From dev-return-40031-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Mon Oct 16 15:35:47 2006 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 95640 invoked from network); 16 Oct 2006 15:35:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Oct 2006 15:35:47 -0000 Received: (qmail 21802 invoked by uid 500); 16 Oct 2006 15:35:43 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 21763 invoked by uid 500); 16 Oct 2006 15:35:43 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Delivered-To: moderator for dev@geronimo.apache.org Received: (qmail 62113 invoked by uid 99); 16 Oct 2006 06:54:33 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) content-class: urn:content-classes:message Subject: RE: Maven's snapshot mechanism is horked (Re: Build error - Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/project-config/pom.xml?) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 16 Oct 2006 08:53:43 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Maven's snapshot mechanism is horked (Re: Build error - Is it from svn commit: r463555 - /geronimo/genesis/trunk/config/project-config/pom.xml?) Thread-Index: AcbvzcVlggedcKOgQWm36Q1+JoNPywBIcCbw From: =?iso-8859-1?Q?J=F6rg_Schaible?= To: "Maven Developers List" Cc: X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi Jason, download of SNAPSHOT dependencies does not work at all in M2.0.4: http://jira.codehaus.org/browse/MNG-1908 - J=F6rg 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 :)). >=20 > 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. >=20 > 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?!?! >=20 > 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. >=20 >=20 >> Another solution is to delete the metadata file from the local >> repository. >=20 > 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. >=20 > 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. >=20 >=20 >> 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..=20 >=20 > 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. >=20 >=20 >> 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. >>=20 >> 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. >=20 > 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.=20 >=20 > 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. >=20 > One thing does look very fishy to me though.... >=20 > > 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=3Dorg.apache.geronimo.genesis.plugins -DartifactId=3Dplugin- > support \ -Dversion=3D1.1-20061013.014841-21 = -Dpackaging=3Djar > -Dfile=3D/ 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 > >=20 > 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". >=20 > --jason >=20 >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org > For additional commands, e-mail: dev-help@maven.apache.org