[
https://issues.apache.org/jira/browse/MDEPLOY-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984477#comment-16984477
]
Andreas Wirooks commented on MDEPLOY-262:
-----------------------------------------
We had two conditions. One was the example above. This was caused by a
Replication error between active and inactive Artifactory instances and a
switch from active to inactive instance. We don't know the cause yet but the
only the md5 checksum file differs from both instances.
The second reason for a 409 from Artifactory is the pom check that disallow
non-conform poms. For details see here:
[https://www.jfrog.com/confluence/display/RTF/Local+Repositories]
Both Artifacts were fixed so i can't retry the ci-job to give more verbose logs.
> Fail on HTTP-Statuscode 409 on Upload instead of warn
> -----------------------------------------------------
>
> Key: MDEPLOY-262
> URL: https://issues.apache.org/jira/browse/MDEPLOY-262
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
> Affects Versions: 3.0.0-M1
> Environment: Debian 10
> Maven 3.6.1
> Artifactory 6.13.1
> Reporter: Andreas Wirooks
> Priority: Major
>
> We have the situation that an upload fails with HTTP-Statuscode 409. Here the
> maven-deploy-plugin should stop with an error. But it only warns and
> continues. This results in missing files or in case of overwriting different
> contents when overwriting did not succeed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
