[
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784186#comment-16784186
]
T Vorschuetz commented on MINSTALL-156:
---------------------------------------
There is another inconsistency to version 2.5.2 that is pointing to the same
issue.
If generatePom is set to true in 2.x.x, a minimalistic POM has been generated
and installed instead of the existing pom.xml. Since 3.0.0-M1 it is not
possible to force a generation of a minimalistic POM even if genratePom is set
to true if a pom is existing. So, in terms the jar file that should be
installed is generated by maven, generatePom does not have any effect anymore.
Let's assume you would like to build a jar that uses a parent pom just for the
creation of the jar itself including some depencies for testing the jar during
the creation and you would like to install and deploy this jar for later use in
further projects without those information, in 2.5.2 it was simply done by
using generatePom=true. Now you have to configure the flatten plugin to
generate a minimalistic POM first.
>From my-point-of-view generatePom is not used in most of the times since
>install-file tries to fetch a POM from inside the jar and this cannot be
>configured not to be done.
Regards,
Tiemo
> 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)
