I guess this could be related, but we almost never use install. Actually, for the LATEST use case, we just commit and have a continuous integration serverthat will just push the resulting artifact to the corporate maven repository (and it will usually be downloaded some minutes after thanks to m2e when asking to "update snapshots"/"update dependencies").
For RELEASE, that's almost the same: they are deployed on one machine and mainly download via the repo by everybody else. Maybe dowloading will correctly set the metadata contrary to mvn install? Cheers. 2008/12/3 Timothy Reilly <[EMAIL PROTECTED]> > Just an observation from today when RELEASE didn't work for us. > > I was at someone's desk who normally build's the parent pom we are > trying to reference as RELEASE. His last build of the pom or perhaps > every build to his local repository is done without mvn install > -DupdateReleaseInfo=true (so false.) The dependent project failed to > build due to not resolving the RELEASE version. He rebuilt the parent > (corporate pom) with -DupdateReleaseInfo=true and then it worked. > > My guess is that when RELEASE version is being resolved it finds the > artifact in the local repository but doesn't find the release metadata > and fails. > Perhaps, while resolving RELEASE all configured repositories need or > should be consulted... Seems like that doesn't happen. (first find fail) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
