[
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764754#comment-16764754
]
Robert Lieske commented on MINSTALL-156:
----------------------------------------
ok, I wrote there:
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.
and:
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
> generatePom=false not working with 3.0.0-M1
> -------------------------------------------
>
> Key: MINSTALL-156
> URL: https://issues.apache.org/jira/browse/MINSTALL-156
> Project: Maven Install Plugin
> Issue Type: Bug
> Affects Versions: 3.0.0-M1
> Reporter: Robert Lieske
> Priority: Major
> Fix For: waiting-for-feedback
>
>
> 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 install:install-file -Dfile=target/test1-1.0-SNAPSHOT.jar
> -DgeneratePom=false}}
> produces:
> {quote}[INFO] --- maven-install-plugin:2.5.2:install-file (default-cli) @
> test1 ---
> [INFO] Installing D:\Workarea\sample\test1\target\test1-1.0-SNAPSHOT.jar to
> C:\Users\xxx\.m2\repository\test1\test1\1.0-SNAPSHOT\test1-1.0-SNAPSHOT.jar
> [INFO]
> ------------------------------------------------------------------------
> {quote}
>
> changing the version of the maven-install-plugin in pom.xml to
> {{<plugin>}}
> {{ <artifactId>maven-install-plugin</artifactId>}}
> {{ <version>3.0.0-M1</version>}}
> {{ </plugin>}}
>
> the same call to
> {{mvn clean package install:install-file -Dfile=target/test1-1.0-SNAPSHOT.jar
> -DgeneratePom=false}}
> produces:
> {quote}[INFO] --- maven-install-plugin:3.0.0-M1:install-file (default-cli) @
> test1 ---
> [INFO] Installing D:\Workarea\sample\test1\target\test1-1.0-SNAPSHOT.jar to
> C:\Users\xxx\.m2\repository\test1\test1\1.0-SNAPSHOT\test1-1.0-SNAPSHOT.jar
> [INFO] Installing
> C:\Users\xxx\AppData\Local\Temp\test1-1.0-SNAPSHOT7157743325898943802.pom to
> C:\Users\xxx\.m2\repository\test1\test1\1.0-SNAPSHOT\test1-1.0-SNAPSHOT.pom
> [INFO]
> ------------------------------------------------------------------------
> {quote}
>
> Which also installs a POM - which is not what we want!
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
