You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Joshua Suereth (JIRA)" <ji...@apache.org> on 2014/04/04 22:51:16 UTC
[jira] [Created] (IVY-1466) overwrite flag causes publish failure
for repositories which autogenerate checksums
Joshua Suereth created IVY-1466:
-----------------------------------
Summary: overwrite flag causes publish failure for repositories which autogenerate checksums
Key: IVY-1466
URL: https://issues.apache.org/jira/browse/IVY-1466
Project: Ivy
Issue Type: Bug
Components: Core
Affects Versions: 2.4.0-RC1
Environment: Ubuntu, Artifactory (maven or ivy), server-generated checksums enabled (since maven also published to the repo)
Reporter: Joshua Suereth
When publishing to a repository with "overwrite" set to false, Ivy publishes the artifact *then* checks to see if the checksum file exists. Since Artifactory automatically creates the checksums, this leads to a failure to publish because the checksum already exists.
I see two possible fixes:
1) Publish signatures/checksums first (I think this may cause other issues with things like nexus/artifactory
2) If you succeed to publish the artifact with the correct overwrite flag, then ALWAYS overwrite when publishing the checksums (since you just pushed the artifact). There's really no reason not to, and it could cause problems if you don't.
We're taking option #2 in sbt, see our hacky workaround here: https://github.com/sbt/sbt/pull/1232/files#diff-b50b19f131fece36d762990bd9d34625R77
--
This message was sent by Atlassian JIRA
(v6.2#6252)