Loading

Publishing succeeds, but returns 409 Conflict when using Exchange Maven Facade API v3

Fecha de publicación: Jul 25, 2025
Solución

SYMPTOM

You are trying to publish an asset to Exchange using Exchange Maven Facade API v3. The asset is published successfully, as shown in the logs: 
[INFO]   ------------------------------------------------------------
[INFO]   Publication status: completed
[INFO]   ------------------------------------------------------------
[INFO]     Steps: 
[INFO]     - Description: Publishing asset
[INFO]     - Status: completed
[INFO]     .........................................
[INFO] 
[INFO]   Your asset has been successfully published to Exchange.
However, a new publication begins after that and Maven tries to republish the asset, resulting in a Build Failure with error 
Failed uploading exchange.eof file: Failed to deploy artifacts: Could not transfer artifact ... 409 Conflict
 

CAUSE

Executing mvn clean deploy is running the publication twice. As the first publication succeeds, there is an asset already deployed with the same asset ID and version, which explains the conflict error. This happens because you are defining 2 plugins to upload the asset.
 

SOLUTION

Remove one of the plugins used to deploy the asset. For instance, you could have both a mule-maven-plugin and an exchange-mule-maven-plugin configured for the same project.

This can also happen when defining one plugin in the parent POM file and one in the child POM file. Any plugins defined in a parent POM file will be inherited by default.
The inherited element defines whether or not this plugin configuration should apply to POMs which inherit from this one, and defaults to true. If this is the case, you can add the property <inherited>false</inherited> to the plugin configuration in the parent POM file.

You can find the complete examples at the exchange-documentation-samples GitHub repository.
 
Número del artículo de conocimiento

001119332

 
Cargando
Salesforce Help | Article