[ 
https://issues.apache.org/jira/browse/MINSTALL-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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 
> {{<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)

Reply via email to