[ 
https://issues.apache.org/jira/browse/MDEPLOY-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965646#comment-17965646
 ] 

Olivier Lamy commented on MDEPLOY-93:
-------------------------------------

This project has moved from Jira to GitHub Issues. This issue was migrated to 
[apache/maven-deploy-plugin#269|https://github.com/apache/maven-deploy-plugin/issues/269].
 

> Deploy plugin does not honor modification of final name by assembly plugin
> --------------------------------------------------------------------------
>
>                 Key: MDEPLOY-93
>                 URL: https://issues.apache.org/jira/browse/MDEPLOY-93
>             Project: Maven Deploy Plugin (Moved to GitHub Issues)
>          Issue Type: Bug
>    Affects Versions: 2.4
>            Reporter: Thorsten Möller
>            Assignee: Benjamin Bentmann
>            Priority: Major
>
> When using the Maven assembly plugin to create an assembly for a project and 
> using "fileName" parameter inside the plugin to change the final name of the 
> assembly this new name will not be used by the deploy plugin. The deploy 
> plugin always uses the default behavior. The following excerpt from a POM 
> illustrates this:
> <groupId>myGoupID</groupId>
> <artifactId>myArtifactID</artifactId>
> <build>
>       <plugins>
>               <plugin>
>                       <groupId>org.apache.maven.plugins</groupId>
>                       <artifactId>maven-assembly-plugin</artifactId>
>                       <configuration>
>                               <descriptors>
>                                       
> <descriptor>src/main/assembly/bin.xml</descriptor>
>                               </descriptors>
>                               <appendAssemblyId>false</appendAssemblyId>
>                               <finalName>foo</finalName>
>                               <tarLongFileMode>gnu</tarLongFileMode>
>                       </configuration>
>                       <executions>
>                               <execution>
>                                       <id>minimal</id>
>                                       <phase>package</phase>
>                                       <goals>
>                                               <goal>single</goal>
>                                       </goals>
>                               </execution>
>                       </executions>
>               </plugin>
>       </plugins>
> </build>
> With this configuration an assembly named "foo.{tar.gz|zip}" will be created 
> in the target folder of the project (note that the artifact is attached 
> because the assembly plugin is attached to the package lifecycle phase). 
> However, when deploying the project file to the distribution repository it 
> will be named "myArtifactId.{tar.gz|zip}", which is the default behavior if 
> "finalName" is not specified. Interesting is that in the local repository the 
> file name always corresponds to what is specified by "fileName", just for the 
> distribution repository the parameter is not honored.
> BTW, the other parameter "appendAssemblyId" is honored correctly, i.e,  
> depending on the boolean value the assembly Id will be appended to the name, 
> or not.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to