I am trying to deploy a bunch of files to Artifactory 3.0.1 using curl, to migrate from some old filesystem-based storage to Artifactory. I can deploy most of the files, but I am having problems deploying POM files. I get the following HTML returned (style stuff removed for clarity):
[user@repo2 ivy-fs]# curl -X PUT http://myserver.com:8081/artifactory/myrepo/com/mycompany/MyArtifact/7.89.1.0/MyArtifact-7.89.1.0.pom --data-binary MyArtifact-7.89.1.0.pom -u username:password -v * About to connect() to myserver.com port 8081 (#0) * Trying 192.168.128.161... connected * Connected to myserver.com (192.168.128.161) port 8081 (#0) * Server auth using Basic with user 'username' > PUT > /artifactory/myrepo/com/mycompany/MyArtifact/7.89.1.0/MyArtifact-7.89.1.0.pom > HTTP/1.1 > Authorization: Basic YnVpbGRlcjpidWlsZGVyMzMxNA== > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 > NSS/3.13.6.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2 > Host: myserver.com:8081 > Accept: */* > Content-Length: 83 > Content-Type: application/x-www-form-urlencoded > < HTTP/1.1 409 Conflict < Server: Artifactory/3.0.1 < X-Artifactory-Id: b9ced078850749b4:-53126a10:140354d395c:-8000 < Content-Type: text/html;charset=utf-8 < Content-Length: 1383 < Date: Thu, 01 Aug 2013 14:23:17 GMT < <html><head><title>Apache Tomcat/7.0.39 - Error report</title></head><body> HTTP Status 409 - Failed to read POM for 'com/mycompany/MyArtifact/7.89.1.0/MyArtifact-7.89.1.0.pom': only whitespace content allowed before start tag and not m (position: START_DOCUMENT seen m... @1:1) . <p>*type* Status report</p><p>*message* <u>Failed to read POM for 'com/mycompany/MyArtifact/7.89.1.0/MyArtifact-7.89.1.0.pom': only whitespace content allowed before start tag and not m (position: START_DOCUMENT seen m... @1:1) .</u></p><p>*description* <u>The request could not be completed due to a conflict with the current state of the resource.</u></p> Apache Tomcat/7.0.39 </body></html> * Connection #0 to host myserver.com left intact * Closing connection #0 I stripped a bunch of comments and namespaces out of the original POM file to make it as basic as I could, and wound up with this: <project> <modelVersion>4.0.0</modelVersion> <groupId>com.mycompany</groupId> <artifactId>myartifact</artifactId> <packaging>zip</packaging> <version>7.89.1.0</version> <description>myartifact.zip</description> <url>http://www.mycompany.com/</url> </project> This is meant to be deployed side-by-side with myartifact.zip in the usual way POM files are stored. But it still fails to deploy and gives the same error as above. Am I doing something wrong? Is this a bug? Thanks, -- Jerry -- View this message in context: http://forums.jfrog.org/Getting-409-error-when-deploying-a-POM-file-through-CURL-tp7578956.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
