[MDEPLOY-251] generatePom=false not working with 3.0.0-M1

[jira-importer]

Robert Lieske opened MDEPLOY-251 and commented

Steps to reproduce:

mvn archetype:generate -DarchetypeGroupId=org.apache.maven.archetypes -DarchetypeArtifactId=maven-archetype-quickstart -DarchetypeVersion=1.4 -DgroupId=test1 -DartifactId=test1 -Dversion=1.0-SNAPSHOT

 

mvn clean package deploy:deploy-file -Dfile=target/test1-1.0-SNAPSHOT.jar -DgeneratePom=false -DgroupId=test1 -DartifactId=test1 -Dversion=1.0-SNAPSHOT -DrepositoryId=snapshotRepository -Durl=${snapshotRepositoryUrl}

produces:

[INFO] --- maven-deploy-plugin:2.8.2:deploy-file (default-cli) @ test1 ---
Downloading from snapshotRepository: http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/maven-metadata.xml
Downloaded from snapshotRepository: http://de01-xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/maven-metadata.xml (583 B at 2.0 kB/s)
Uploading to snapshotRepository: http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/test1-1.0-20190204.162443-2.jar
Uploaded to snapshotRepository: http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/test1-1.0-20190204.162443-2.jar (2.4 kB at 8.1 kB/s)
Downloading from snapshotRepository: http://xxx/repository/snapshots/test1/test1/maven-metadata.xml
Downloaded from snapshotRepository: http://xxx/repository/snapshots/test1/test1/maven-metadata.xml (268 B at 1.8 kB/s)
Uploading to snapshotRepository: http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/maven-metadata.xml
Uploaded to snapshotRepository: http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/maven-metadata.xml (583 B at 3.3 kB/s)
Uploading to snapshotRepository: http://xxx/repository/snapshots/test1/test1/maven-metadata.xml
Uploaded to snapshotRepository: http://xxx/repository/snapshots/test1/test1/maven-metadata.xml (268 B at 1.4 kB/s)
[INFO] ------------------------------------------------------------------------

 

changing the version of the maven-deploy-plugin in pom.xml to 

<plugin>
<artifactId>maven-deploy-plugin</artifactId>
<version>3.0.0-M1</version>
</plugin>

 

the same call to

mvn clean package deploy:deploy-file -Dfile=target/test1-1.0-SNAPSHOT.jar -DgeneratePom=false -DgroupId=test1 -DartifactId=test1 -Dversion=1.0-SNAPSHOT -DrepositoryId=snapshotRepository -Durl=${snapshotRepositoryUrl}

produces:

[INFO] --- maven-deploy-plugin:3.0.0-M1:deploy-file (default-cli) @ test1 ---
Downloading from snapshotRepository: http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/maven-metadata.xml
Downloaded from snapshotRepository: http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/maven-metadata.xml (583 B at 1.6 kB/s)
Uploading to snapshotRepository: http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/test1-1.0-20190204.162607-3.jar
Uploaded to snapshotRepository: http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/test1-1.0-20190204.162607-3.jar (2.4 kB at 7.7 kB/s)
Uploading to snapshotRepository: http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/test1-1.0-20190204.162607-3.pom
Uploaded to snapshotRepository: http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/test1-1.0-20190204.162607-3.pom (2.7 kB at 9.6 kB/s)
Downloading from snapshotRepository: http://xxx/repository/snapshots/test1/test1/maven-metadata.xml
Downloaded from snapshotRepository: http://xxx/repository/snapshots/test1/test1/maven-metadata.xml (268 B at 2.6 kB/s)
Uploading to snapshotRepository: http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/maven-metadata.xml
Uploaded to snapshotRepository: http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/maven-metadata.xml (754 B at 4.0 kB/s)
Uploading to snapshotRepository: http://xxx/repository/snapshots/test1/test1/maven-metadata.xml
Uploaded to snapshotRepository: http://xxx/repository/snapshots/test1/test1/maven-metadata.xml (268 B at 1.5 kB/s)
[INFO] ------------------------------------------------------------------------

 

Which also deploys a POM - which is not what we want!

 

NOTE: there is a similar issue with the maven-install-plugin

---

Affects: 3.0.0-M1

Remote Links:

• GitHub Pull Request #185
  

[jira-importer]

Robert Lieske commented

Hi,

I commented on your merge commit.

In the meantime I found out, that the uploaded POM does not have the content I want, so I need to fix this first, so that I can provide a corrected sample for my use case.

Nevertheless (regardless what my motivation is to disable POM generation), the current versions of the maven-install-plugin and maven-deploy-plugin do not behave as documented here https://maven.apache.org/plugins/maven-deploy-plugin/examples/disabling-generic-pom.html.

To describe my motivation (copied from the other bugreport https://issues.apache.org/jira/browse/MINSTALL-156):

I want to deploy both the created JAR and the JAR-with-dependencies to the repository. As the release repository does not allow to upload the same POM twice, I have to configure the maven-deploy-plugin to skip generation of POM when uploading the JAR-with-dependencies.

As a side note: the uploaded artifacts have to have a different name, so I need to configure everything by hand.

 

[jira-importer]

Robert Lieske commented

I have updated my sample to fix the issue with the content of the POM (artifact name differs from filename).

Basicly you missed the point, that the uploaded artifacts should have a different name.

I have changed the code upload a released version, so you'll see the problem (overwriting uploaded POM is not allowed), when you change the plugin-version to 3.0.0-M1. To make the sample work for you, supply 'releaseRepositoryUrl' and 'releaseRepository' with credentials in your settings.xml