[jira] [Commented] (MINSTALL-156) generatePom=false not working with 3.0.0-M1
[
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17081214#comment-17081214
]
Václav Haisman commented on MINSTALL-156:
-
What [~TVO] describes is exactly my case. See MINSTALL-160. We build OSGi
bundles with complex POM but we want minimal POM installed. That has stopped
working with the latest plugin version.
> 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
> {{}}
> {{ maven-install-plugin}}
> {{ 3.0.0-M1}}
> {{ }}
>
> 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
(v8.3.4#803005)
[jira] [Commented] (MINSTALL-156) generatePom=false not working with 3.0.0-M1
[
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
> {{}}
> {{ maven-install-plugin}}
> {{ 3.0.0-M1}}
> {{ }}
>
> 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)
[jira] [Commented] (MINSTALL-156) generatePom=false not working with 3.0.0-M1
[
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767117#comment-16767117
]
Karl Heinz Marbaise commented on MINSTALL-156:
--
First as you already realized in your logging output you see exactly what
happens. The {{finalName}} will only change the name for the artifact in
{{target}} directory. During the installation you see the result:
{code}
[INFO] Installing D:\Workarea\sample\sample2\test1\target\blabla.jar to
C:\Users\xxx\.m2\repository\test1\test1\1.0-SNAPSHOT\test1-1.0-SNAPSHOT.jar
{code}
The install plugin converts the artifact to follow the naming schema:
{{artifactId-version-classifier.extension}} which is required.
Furthermore the deploy plugin does the same. Furthermore changing the naming
schema is simply not possible.
If it would be possible this would break the whole remote repository.
Apart from that you seemed to be misunderstanding the {{generatePom}}
configuration cause it will generate a pom file if you don't offer one yourself
with {{install-file}} or {{deploy-file}} goals.
So unfortunately I don't see any issue here. The goals {{install-file}} and
{{deploy-file}} behave as expected based on the docs and breaking functionality
is something which can of course happen if we have a major version change...
> 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
> {{}}
> {{ maven-install-plugin}}
> {{ 3.0.0-M1}}
> {{ }}
>
> 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)
[jira] [Commented] (MINSTALL-156) generatePom=false not working with 3.0.0-M1
[
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16764851#comment-16764851
]
Robert Lieske commented on MINSTALL-156:
I might have tweaked the things a bit to fit my needs. ;)
When I don't configure the maven-install-plugin and maven-deploy-plugin, the
artifacts are renamed (as per your example):
{{[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ test1 ---}}
{{[INFO] Installing
D:\Workarea\sample\sample2\test1\target\{color:#d04437}blabla.jar{color} to
C:\Users\xxx\.m2\repository\test1\test1\{color:#d04437}1.0-SNAPSHOT\test1-1.0-SNAPSHOT.jar{color}}}
{{[INFO] Installing D:\Workarea\sample\sample2\test1\pom.xml to
C:\Users\xxx\.m2\repository\test1\test1\1.0-SNAPSHOT\{color:#d04437}test1-1.0-SNAPSHOT.pom{color}}}
{{[INFO] Installing
D:\Workarea\sample\sample2\test1\target\{color:#d04437}blabla-jar-with-dependencies.jar{color}
to
C:\Users\xxx\.m2\repository\test1\test1\1.0-SNAPSHOT\{color:#d04437}test1-1.0-SNAPSHOT-jar-with-dependencies.jar{color}}}
and consequently:
{{[INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ test1 ---}}
{{Uploading to snapshotRepository:
http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/{color:#d04437}test1-1.0-20190211.100531-1.jar{color}}}
{{Uploading to snapshotRepository:
http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/{color:#d04437}test1-1.0-20190211.100531-1.pom{color}}}
{{Uploading to snapshotRepository:
http://xxx/repository/snapshots/test1/test1/1.0-SNAPSHOT/{color:#d04437}test1-1.0-20190211.100531-1-jar-with-dependencies.jar{color}}}
To avoid the renaming, the plugins have to be configured.
The old versions allow to configure everything as required. The new ones don't
(i.e. behave different).
I can just stick to the old versions (and leave a comment in my POM, why), as
they work as I need them to.
Regardless of my motivations / requirements: If you have a parameter named
, set to false, and still get a POM generated, installed and
uploaded, this is not to be expected!
> 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
> {{}}
> {{ maven-install-plugin}}
> {{ 3.0.0-M1}}
> {{ }}
>
> 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)
[jira] [Commented] (MINSTALL-156) generatePom=false not working with 3.0.0-M1
[
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16764767#comment-16764767
]
Karl Heinz Marbaise commented on MINSTALL-156:
--
Unfortunately you seemed to misunderstand the description and intention of
https://maven.apache.org/plugins/maven-deploy-plugin/examples/disabling-generic-pom.html
Second if you like to deploy an jar-with-dependencies which is created by the
maven-assembly-plugin you never need to configure maven-install-plugin neither
maven-deploy-plugin in the way as in your example...
Furthermore uploaded artifacts follow a naming schema which can't be changed.
And there is no way to configure things like that...
> 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
> {{}}
> {{ maven-install-plugin}}
> {{ 3.0.0-M1}}
> {{ }}
>
> 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)
[jira] [Commented] (MINSTALL-156) generatePom=false not working with 3.0.0-M1
[
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
> {{}}
> {{ maven-install-plugin}}
> {{ 3.0.0-M1}}
> {{ }}
>
> 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)
[jira] [Commented] (MINSTALL-156) generatePom=false not working with 3.0.0-M1
[
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16764720#comment-16764720
]
Karl Heinz Marbaise commented on MINSTALL-156:
--
Why ? We already discuss here? So why going into an other one?
> 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
> {{}}
> {{ maven-install-plugin}}
> {{ 3.0.0-M1}}
> {{ }}
>
> 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)
[jira] [Commented] (MINSTALL-156) generatePom=false not working with 3.0.0-M1
[
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16764717#comment-16764717
]
Robert Lieske commented on MINSTALL-156:
I have updated my sample.
I will continue discussion in the other bug report, so I dont have to duplicate
everything.
> 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
> {{}}
> {{ maven-install-plugin}}
> {{ 3.0.0-M1}}
> {{ }}
>
> 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)
[jira] [Commented] (MINSTALL-156) generatePom=false not working with 3.0.0-M1
[
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761665#comment-16761665
]
Karl Heinz Marbaise commented on MINSTALL-156:
--
I have taken a short look into the pom file. So now the real question is: Why
do you have configured maven-install-plugin and maven-deploy-plugin? The
destination repository where all artifacts will be deployed to is defined by
{{distributionManagement}} which is not defined here so you have to.
Furthermore is the question why you have configured maven-assembly-plugin but
configured {{false}} please explain what your use case is?
So in the end you can simply define a {{distributionManagement}} in your pom
file and remove {{false}} from the maven-assembly-plugin
everything will be installed/deployed via {{mvn clean deploy}} or {{mvn clean
install}} ?
I have made PR to your repository take a deep look into the result... cause it
sounds like you have a misunderstanding of how Maven works
> 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
>
> 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
> {{}}
> {{ maven-install-plugin}}
> {{ 3.0.0-M1}}
> {{ }}
>
> 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)
[jira] [Commented] (MINSTALL-156) generatePom=false not working with 3.0.0-M1
[
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761659#comment-16761659
]
Robert Lieske commented on MINSTALL-156:
I uploaded a sample project to:
https://github.com/robert9876/test1.git
> 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
>
> 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
> {{}}
> {{ maven-install-plugin}}
> {{ 3.0.0-M1}}
> {{ }}
>
> 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)
[jira] [Commented] (MINSTALL-156) generatePom=false not working with 3.0.0-M1
[
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761613#comment-16761613
]
Karl Heinz Marbaise commented on MINSTALL-156:
--
In a Maven project you usually do {{mvn clean deploy}} and never call
{{install:install-file}} separately. This is true for install which means
simply {{mvn clean install}} as well as for deploy so you have to configure the
creation of the jar-with-dependencies via maven-assembly-plugin correctly which
results in just calling {{mvn clean deploy}} and it does not matter if you do
that for a {{SNAPSHO}} or for an release.
> 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
>
> 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
> {{}}
> {{ maven-install-plugin}}
> {{ 3.0.0-M1}}
> {{ }}
>
> 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)
[jira] [Commented] (MINSTALL-156) generatePom=false not working with 3.0.0-M1
[
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761601#comment-16761601
]
Robert Lieske commented on MINSTALL-156:
Hi Karl Heinz,
Actually I don't care much about the Install, its the deploy that bothers me.
The issue is just similar.
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:
{code:java}
blabla
...
org.apache.maven.plugins
maven-install-plugin
default-install
true
install-small-file
install
install-file
${project.build.directory}/${project.build.finalName}.jar
${project.build.finalName}
${project.groupId}
${project.version}
install-fat-file
install
install-file
${project.build.directory}/${project.build.finalName}-jar-with-dependencies.jar
false
${project.build.finalName}
${project.groupId}
${project.version}
jar-with-dependencies
org.apache.maven.plugins
maven-deploy-plugin
default-deploy
true
deploy-small-file
deploy
deploy-file
${targetrepositoryId}
${targetrepositoryUrl}
${project.build.directory}/${project.build.finalName}.jar
${project.build.finalName}
${project.groupId}
${project.version}
deploy-fat-file
deploy
deploy-file
${targetrepositoryId}
${targetrepositoryUrl}
${project.build.directory}/${project.build.finalName}-jar-with-dependencies.jar
false
${project.build.finalName}
${project.groupId}
${project.version}
jar-with-dependencies
{code}
> 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
>
> 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
> {{}}
> {{ maven-install-plugin}}
> {{ 3.0.0-M1}}
> {{ }}
>
> 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)
[jira] [Commented] (MINSTALL-156) generatePom=false not working with 3.0.0-M1
[
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761572#comment-16761572
]
Karl Heinz Marbaise commented on MINSTALL-156:
--
Can you explain why you want to install an artifact without a pom file ?
> 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
>
> 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
> {{}}
> {{ maven-install-plugin}}
> {{ 3.0.0-M1}}
> {{ }}
>
> 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)
[jira] [Commented] (MINSTALL-156) generatePom=false not working with 3.0.0-M1
[
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760594#comment-16760594
]
Robert Lieske commented on MINSTALL-156:
If I manually delete the META-INF directory inside the JAR file, the POM is not
installed, even with 3.0.0-M1 version. But I need the META-INF, so this is no
solution.
Version 2.5.2 works as documented (see
[https://maven.apache.org/plugins/maven-deploy-plugin/examples/disabling-generic-pom.html]),
while 3.0.0-M1 does not. Downgrading solves the problem at hand for me.
There is a similar issue with the maven-deploy-plugin
(https://issues.apache.org/jira/browse/MDEPLOY-251), that I'm really interested
- deploying to a release repository does not allow to deploy the same POM twice
(which is from my real-world use, the sample above is just provided to easily
reproduce the buggy behaviour). The bug report here is just because (and it is
similar).
> 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
>
> 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
> {{}}
> {{ maven-install-plugin}}
> {{ 3.0.0-M1}}
> {{ }}
>
> 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)
[jira] [Commented] (MINSTALL-156) generatePom=false not working with 3.0.0-M1
[
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16760268#comment-16760268
]
Witold Markowski commented on MINSTALL-156:
---
This behavior may be an expected behavior. It looks like *3.0.0-M1* will
install *pom* file always, if the *pom* is available from the inside of the
installed *jar* file. When the artifact is built by Maven, it will put the
*pom* in the *META-INF* directory inside of the jar. This *pom* file will be
installed always no matter what *generatePom* says.
However *generatePom* comes into action when you want to install a *jar* file
which doesn't contain any *META-INF* inside. [~robert12345], please do a simple
test:
* delete whole *META-INF* from the inside of your
*target/test1-1.0-SNAPSHOT.jar*
* execute *mvn
org.apache.maven.plugins:maven-install-plugin:3.0.0-M1:install-file
-Dfile=target/test1-1.0-SNAPSHOT.jar -DgroupId=test1 -DartifactId=test1
-Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dgene ratePom=false*
In my test *pom* file is not generated by *maven-install-plugin* as below:
{noformat}
$ mvn org.apache.maven.plugins:maven-install-plugin:3.0.0-M1:install-file
-Dfile=target/test1-1.0-SNAPSHOT.jar -DgroupId=test1 -DartifactId=test1
-Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dgene ratePom=false
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building test1 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-install-plugin:3.0.0-M1:install-file (default-cli) @ test1 ---
[INFO] pom.xml not found in test1-1.0-SNAPSHOT.jar
[INFO] Installing
C:\Users\wmarkowski\dev-test\sources\test1\target\test1-1.0-SNAPSHOT.jar to
C:\Users\wmarkowski\.m2\repository\test1\test1\1.0-SNAPSHOT\test1-1.0-SNAPSHOT.jar
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 0.730 s
[INFO] Finished at: 2019-02-04T23:13:56+01:00
[INFO] Final Memory: 9M/245M
[INFO]
{noformat}
>From the other hand, this behavior may break the back compatibility with
>*2.5.2* version, where it was possible to *NOT* to install *pom*. The question
>is: does *3.0.0-M1* need to be as much back compatible with *2.5.2*? Second
>thing: it seems to be a good idea to have *pom* as well installed; maven will
>have then all information about dependencies used by the installed *jar*.
> 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
>
> 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
> {{}}
> {{ maven-install-plugin}}
> {{ 3.0.0-M1}}
> {{ }}
>
> 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)
