I figured out my problem. For the record I was kicking off a maven build from
my box in this scenario. The main problem was that I incorrectly specified
the new artifact that I added to my pom. The version of the artifact was
"1.3.1.RELEASE" and I had typed it as "1.3.1-RELEASE". Changing that fixed
the problem.
But why the strange warning in the Artifactory log? I think Artifactory
responded the way it did because in my project pom I specified the
repositories as follows:
<repositories>
<repository>
<id>foo-repo</id>
<name>Foo Repo</name>
<url>http://ci.foo.com/artifactory/repo</url>
</repository>
<repository>
<id>foo-snapshots</id>
<name>Foo Snapshots</name>
<url>http://ci.foo.com/artifactory/foo-snapshots</url>
<snapshots>
<enabled>true</enabled>
<updatePolicy>interval:1</updatePolicy>
</snapshots>
</repository>
</repositories>
Because the second repository did not specify that releases were not
accepted once maven failed on the first repo it tried the second and got the
"due to its snapshot/release handling" warning in the Artifactory log, and
Artifactory is right to give that warning imho.
To correct this I changed the second repo in my pom files as follows:
<repositories>
<repository>
<id>foo-repo</id>
<name>Foo Repo</name>
<url>http://ci.foo.com/artifactory/repo</url>
</repository>
<repository>
<id>foo-snapshots</id>
<name>Foo Snapshots</name>
<url>http://ci.foo.com/artifactory/foo-snapshots</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>interval:1</updatePolicy>
</snapshots>
</repository>
</repositories>
Then I had the thought that since the first repo in my pom is Artifactory's
virtual repo of everything that I didn't even need to specify the second
repo and instead the following has been working just fine:
<repositories>
<repository>
<id>foo-repo</id>
<name>Foo Repo</name>
<url>http://ci.foo.com/artifactory/repo</url>
<snapshots>
<updatePolicy>interval:1</updatePolicy>
</snapshots>
</repository>
</repositories>
--
View this message in context:
http://forums.jfrog.org/Repository-rejected-artifact-due-to-its-snapshot-release-handling-policy-tp6513457p6518206.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
