Hi Noam (and all),
Yes, my apologies for the mistake: I meant HTTP code 409, not 509. Also,
sorry for the double post-I thought that the list had rejected my first
submission because I submitted it before confirming my subscription, but both
posts ended up being accepted later.
In any case, the server logs are very helpful. The problem was the revision
number in the POM; Ivy used "working@hostname" as the revision number in the
POM, instead of the actual revision number being deployed. Getting Ivy to set
that correctly was a simple fix. With that done, the first method mentioned in
my original email was the one that worked (I would prefer to simply substitute
the POM file for the Ivy file, but Ivy complains that it is not a valid Ivy
file, so the working solution is to publish the POM as an artifact and suppress
publishing the Ivy file.
Thanks,
Doug Glidden
The Boeing Company
(703) 317-7523
From: Noam Y. Tenne [mailto:[email protected]]
Sent: Wednesday, September 07, 2011 2:33 AM
To: [email protected]
Subject: Re: [Artifactory-users] Cannot publish a POM to Artifactory from Ivy
(HTTP 509: Conflict)
Hi,
Do you mean by any chance HTTP response code 409? 509 isn't specified in the
RFC to my knowledge.
Receiving a conflict response from a POM deployment can indicate a number of
things:
1. The POM content is invalid (bad XML perhaps?).
2. The path to which the pom is deployed to does not match the GAVC it
specifies.
Can you check that the generated POM is valid and that it gets deployed to the
correct path?
Also, do you see any indication of the error in Artifactory's log file when
this error occurs?
HTH,
Noam
On Tue, Sep 6, 2011 at 8:58 PM, Glidden, Douglass A
<[email protected]<mailto:[email protected]>> wrote:
I am trying to publish artifacts to an internal, m2compatible Artifactory
repository using Ivy. I can publish the artifacts themselves without a
problem, but I cannot seem to publish the accompanying POM file to the
repository.
I have tried two methods of publishing the POM:
* Specify an extra artifact in ivy.xml for the POM file, and then
publish with publishivy="false" (to disable publishing the ivy.xml file).
* Use the ivypattern of the resolver and the srcivypattern to
substitute the POM file for the ivy.xml file when publishing.
Both methods have the same result. When Ivy attempts to upload the POM file to
the Artifactory server, the server responds with the HTTP response code 509:
Conflict. Can someone please explain to me the correct means of publishing an
artifact with its POM to an m2compatible Artifactory repository?
Thanks,
Doug Glidden
Software Engineer
The Boeing Company
[email protected]<mailto:[email protected]>
------------------------------------------------------------------------------
Malware Security Report: Protecting Your Business, Customers, and the
Bottom Line. Protect your business and customers by understanding the
threat from malware and how it can impact your online business.
http://www.accelacomm.com/jaw/sfnl/114/51427462/
_______________________________________________
Artifactory-users mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/artifactory-users
------------------------------------------------------------------------------
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
