[
https://issues.apache.org/jira/browse/MDEPLOY-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17899179#comment-17899179
]
Juan Antonio Brena Moral commented on MDEPLOY-318:
--------------------------------------------------
Hi,
I noticed that the ticket continue opened and I would like to report than 2
weeks ago using the latest maven plugin 3.1.3 included in {_}Spring Boot
3.3.4{_}, it is not working for us when we try to deploy to JFROG Artifactory
or Azure Packages with Azure Pipelines.
The workaround that we had to do in order to deploy was to downgrade the plugin
to {{maven-deploy-plugin:3.1.1:}}
{{ - task: Maven@4}}
{{ displayName: Deploy jar}}
{{ inputs:}}
{{ mavenPomFile: 'pom.xml'}}
{{ goals: 'jar:jar
org.apache.maven.plugins:maven-deploy-plugin:3.1.1:deploy'}}
{{ ...}}
I would like to collaborate to evolve the plugin and help in the testing.
Juan Antonio
> 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
> Reporter: Michaël
> Assignee: Slawomir Jaranowski
> Priority: Major
> Attachments: pom.xml, test-maven-deploy-0.0.1.zip,
> test-maven-deploy-0.0.2.zip, test-maven-parent-0.0.1.pom,
> test-maven-parent-0.0.2.pom
>
>
> hi, i'm using spring-boot, and upon updating to 3.2.6 i noticed that my
> parent pom was uploaded corrupted.
> {{[FATAL] Non-parseable POM
> ~/.m2/repository/nl/intractief/intr-parent/7.1.5/intr-parent-7.1.5.pom: only
> whitespace content allowed before start tag and not P (position:
> START_DOCUMENT seen P... @1:2) @
> ~/.m2/repository/nl/intractief/intr-parent/7.1.5/intr-parent-7.1.5.pom, line
> 1, column 2}}
>
> * the same parent pom was correctly published using spring-boot 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 there is 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)
