I managed to get this working by having the artifactory name artifacts
uniquely (with timestamp).
Don't know if this is the proper way, but it's working so far.
2009/5/18 Anders Hammar and...@hammar.net
Could it be an Artifactory bug? What's the content of the
maven-metadata.xml file of the
Hi Anders,
Thanks a lot.. You are right, I need to specifically specify to update on
each build.
When I do so, I can see from Maven's output that it's trying to download my
POM again, but it actually isn't.
The POM changed in the remote repository, but it remained the same local
repository. I'm
Could it be an Artifactory bug? What's the content of the
maven-metadata.xml file of the
seta.config:seta-general-configuration:1.0-SNAPSHOT artifact?
On Mon, May 18, 2009 at 09:24, Bocalinda bocali...@gmail.com wrote:
Hi Anders,
Thanks a lot.. You are right, I need to specifically specify to
Hi List,
According to the documentation, when specifying a version as -SNAPSHOT,
Maven downloads the artifact on each build.
I specify:
parent
groupIdconfig/groupId
artifactIdseta-general-configuration/artifactId
version1.0-SNAPSHOT/version
/parent
and expected Maven to download
I think SNAPSHOTs are only updated once a day or so, not for every
build. You can force it through mvn -U or by settings updatePolicy
in your settings.xml:
http://maven.apache.org/ref/2.0.8/maven-settings/settings.html#class_releases
Here's a blog about this:
