[ https://issues.apache.org/jira/browse/MDEPLOY-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17851788#comment-17851788 ]
Michaël commented on MDEPLOY-318: --------------------------------- ok * [https://gitlab.com/tub/test-maven-deploy/-/releases/0.0.1] this is the faulty deployed version * [https://gitlab.com/tub/test-maven-deploy/-/releases/0.0.2] this is the correct one do you want me > 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 > Priority: Major > > 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 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)