[jira] [Updated] (MDEPLOY-318) version 3.1.2 is uploading jar files to wrong endpoints

["Michaël (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MDEPLOY-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michaël updated MDEPLOY-318:
----------------------------
    Summary: version 3.1.2 is uploading jar files to wrong endpoints  (was: version 3.1.2 is uploading jar files to pom endpoints?)

> version 3.1.2 is uploading jar files to wrong endpoints
> -------------------------------------------------------
>
>                 Key: MDEPLOY-318
>                 URL: https://issues.apache.org/jira/browse/MDEPLOY-318
>             Project: Maven Deploy Plugin
>          Issue Type: Bug
>    Affects Versions: 3.1.2
>         Environment: spring-boot, gitlab / nexus
>            Reporter: Michaël
>            Priority: Major
>
> hi, i'm using spring-boot, and upon updating to 3.2.6 i noticed that my parent poms were uploaded corrupted.
>  * the same parent pom is correct in 3.2.5
>  * the parent pom is correct before publishing in the pipeline (manually checked the target folder).
>  * after publishing i see binary stuff as pom (guess: zipped binary content)
>  * setting the maven-deploy-plugin.version in the project to 3.1.1 solves the issue.
> in the spring-boot project i created an issue about this (see external issue link) and found another similar issue with a functional workaround.
> we think the're an issue with the deployment endpoints in version 3.1.2 it seems the jars end up at the pom endpoints
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)