You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2008/07/04 21:01:26 UTC
[jira] Created: (MASSEMBLY-338) Overridden artifact finalName is
ignored by the assembly plugin.
Overridden artifact finalName is ignored by the assembly plugin.
----------------------------------------------------------------
Key: MASSEMBLY-338
URL: http://jira.codehaus.org/browse/MASSEMBLY-338
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-1
Environment: Maven 2.0.9, JDK 6, WinXP SP2
Reporter: Michael Osipov
Attachments: assemblyMapping.png
I have a multimodule project.
groupId: net.fckeditor
Parent ArtifactId: fckeditor-java
1. module ArtifactId: java-core; finalName "fckeditor-${artifactId}-${version}" though => e.g. fckeditor-java-core-2.4-SNAPSHOT
2. module ArtifactId: java-demo; finalName "fckeditor-${artifactId}-${version}" though
I did create a bin assembly. The assembly contains the jars but their names do not correspond to the overridden finalNames.
An example picture is attached and the project can be checked out at our [trac|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk] and the [SVN|http://svn.fckeditor.net/FCKeditor.Java/trunk/] directly.
Checkout the [bin.xml|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk/src/main/assembly/bin.xml] and comment out the first outputFileNameMapping and run "mvn clean site package assembly:assembly".
You should be able to reproduce the problem.
I did find a workaround for the problem by defining the outputFileNameMapping as same as in the modules poms. This works just because all modules have the same finalName remapping.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MASSEMBLY-338) Overridden artifact finalName is
ignored by the assembly plugin.
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MASSEMBLY-338.
--------------------------------
Resolution: Won't Fix
Fix Version/s: 2.2-beta-6
Assignee: John Casey
using outputFileNameMapping is the correct approach, since the finalName parameter in a Maven build pertains only to the filename in the target directory, not to any of the subsequent handling by consumers.
An interesting idea would be to use ${artifact.build.finalName}-${artifact.baseVersion}.${artifact.extension}, which should work in 2.2-beta-6 and later.
> Overridden artifact finalName is ignored by the assembly plugin.
> ----------------------------------------------------------------
>
> Key: MASSEMBLY-338
> URL: http://jira.codehaus.org/browse/MASSEMBLY-338
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Maven 2.0.9, JDK 6, WinXP SP2
> Reporter: Michael Osipov
> Assignee: John Casey
> Fix For: 2.2-beta-6
>
> Attachments: assemblyMapping.png
>
>
> I have a multimodule project.
> groupId: net.fckeditor
> Parent ArtifactId: fckeditor-java
> 1. module ArtifactId: java-core; finalName "fckeditor-${artifactId}-${version}" though => e.g. fckeditor-java-core-2.4-SNAPSHOT
> 2. module ArtifactId: java-demo; finalName "fckeditor-${artifactId}-${version}" though
> I did create a bin assembly. The assembly contains the jars but their names do not correspond to the overridden finalNames.
> An example picture is attached and the project can be checked out at our [trac|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk] and the [SVN|http://svn.fckeditor.net/FCKeditor.Java/trunk/] directly.
> Checkout the [bin.xml|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk/src/main/assembly/bin.xml] and comment out the first outputFileNameMapping and run "mvn clean site package assembly:assembly".
> You should be able to reproduce the problem.
> I did find a workaround for the problem by defining the outputFileNameMapping as same as in the modules poms. This works just because all modules have the same finalName remapping.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-338) Overridden artifact finalName is
ignored by the assembly plugin.
Posted by "Michael Osipov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150506#action_150506 ]
Michael Osipov commented on MASSEMBLY-338:
------------------------------------------
Are you refering to: http://maven.apache.org/plugins/maven-assembly-plugin/assembly-mojo.html#finalName
this finalName refers to <name>.zip for instance not the artifacts inside that zip.
> Overridden artifact finalName is ignored by the assembly plugin.
> ----------------------------------------------------------------
>
> Key: MASSEMBLY-338
> URL: http://jira.codehaus.org/browse/MASSEMBLY-338
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Maven 2.0.9, JDK 6, WinXP SP2
> Reporter: Michael Osipov
> Attachments: assemblyMapping.png
>
>
> I have a multimodule project.
> groupId: net.fckeditor
> Parent ArtifactId: fckeditor-java
> 1. module ArtifactId: java-core; finalName "fckeditor-${artifactId}-${version}" though => e.g. fckeditor-java-core-2.4-SNAPSHOT
> 2. module ArtifactId: java-demo; finalName "fckeditor-${artifactId}-${version}" though
> I did create a bin assembly. The assembly contains the jars but their names do not correspond to the overridden finalNames.
> An example picture is attached and the project can be checked out at our [trac|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk] and the [SVN|http://svn.fckeditor.net/FCKeditor.Java/trunk/] directly.
> Checkout the [bin.xml|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk/src/main/assembly/bin.xml] and comment out the first outputFileNameMapping and run "mvn clean site package assembly:assembly".
> You should be able to reproduce the problem.
> I did find a workaround for the problem by defining the outputFileNameMapping as same as in the modules poms. This works just because all modules have the same finalName remapping.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MASSEMBLY-338) Overridden artifact finalName is
ignored by the assembly plugin.
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MASSEMBLY-338:
--------------------------------------
Fix Version/s: (was: 2.2)
> Overridden artifact finalName is ignored by the assembly plugin.
> ----------------------------------------------------------------
>
> Key: MASSEMBLY-338
> URL: http://jira.codehaus.org/browse/MASSEMBLY-338
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Maven 2.0.9, JDK 6, WinXP SP2
> Reporter: Michael Osipov
> Assignee: John Casey
> Attachments: assemblyMapping.png
>
>
> I have a multimodule project.
> groupId: net.fckeditor
> Parent ArtifactId: fckeditor-java
> 1. module ArtifactId: java-core; finalName "fckeditor-${artifactId}-${version}" though => e.g. fckeditor-java-core-2.4-SNAPSHOT
> 2. module ArtifactId: java-demo; finalName "fckeditor-${artifactId}-${version}" though
> I did create a bin assembly. The assembly contains the jars but their names do not correspond to the overridden finalNames.
> An example picture is attached and the project can be checked out at our [trac|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk] and the [SVN|http://svn.fckeditor.net/FCKeditor.Java/trunk/] directly.
> Checkout the [bin.xml|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk/src/main/assembly/bin.xml] and comment out the first outputFileNameMapping and run "mvn clean site package assembly:assembly".
> You should be able to reproduce the problem.
> I did find a workaround for the problem by defining the outputFileNameMapping as same as in the modules poms. This works just because all modules have the same finalName remapping.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-338) Overridden artifact finalName is
ignored by the assembly plugin.
Posted by "Geert Schuring (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150495#action_150495 ]
Geert Schuring commented on MASSEMBLY-338:
------------------------------------------
I have the same problem. According to the assembly plugin documentation, one should be able to set the finalName in the configuration of the plugin.
See [http://maven.apache.org/plugins/maven-assembly-plugin/assembly-mojo.html]
However, the assembly plugin ignores this. I need the jar file the have a certain name, which is currently impossible.
> Overridden artifact finalName is ignored by the assembly plugin.
> ----------------------------------------------------------------
>
> Key: MASSEMBLY-338
> URL: http://jira.codehaus.org/browse/MASSEMBLY-338
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Maven 2.0.9, JDK 6, WinXP SP2
> Reporter: Michael Osipov
> Attachments: assemblyMapping.png
>
>
> I have a multimodule project.
> groupId: net.fckeditor
> Parent ArtifactId: fckeditor-java
> 1. module ArtifactId: java-core; finalName "fckeditor-${artifactId}-${version}" though => e.g. fckeditor-java-core-2.4-SNAPSHOT
> 2. module ArtifactId: java-demo; finalName "fckeditor-${artifactId}-${version}" though
> I did create a bin assembly. The assembly contains the jars but their names do not correspond to the overridden finalNames.
> An example picture is attached and the project can be checked out at our [trac|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk] and the [SVN|http://svn.fckeditor.net/FCKeditor.Java/trunk/] directly.
> Checkout the [bin.xml|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk/src/main/assembly/bin.xml] and comment out the first outputFileNameMapping and run "mvn clean site package assembly:assembly".
> You should be able to reproduce the problem.
> I did find a workaround for the problem by defining the outputFileNameMapping as same as in the modules poms. This works just because all modules have the same finalName remapping.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-338) Overridden artifact finalName is
ignored by the assembly plugin.
Posted by "Geert Schuring (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150590#action_150590 ]
Geert Schuring commented on MASSEMBLY-338:
------------------------------------------
Yeah i mean finalName, and i know it's meant to set the final name of the artifact being build. Which is exactly what i need.
> Overridden artifact finalName is ignored by the assembly plugin.
> ----------------------------------------------------------------
>
> Key: MASSEMBLY-338
> URL: http://jira.codehaus.org/browse/MASSEMBLY-338
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: Maven 2.0.9, JDK 6, WinXP SP2
> Reporter: Michael Osipov
> Attachments: assemblyMapping.png
>
>
> I have a multimodule project.
> groupId: net.fckeditor
> Parent ArtifactId: fckeditor-java
> 1. module ArtifactId: java-core; finalName "fckeditor-${artifactId}-${version}" though => e.g. fckeditor-java-core-2.4-SNAPSHOT
> 2. module ArtifactId: java-demo; finalName "fckeditor-${artifactId}-${version}" though
> I did create a bin assembly. The assembly contains the jars but their names do not correspond to the overridden finalNames.
> An example picture is attached and the project can be checked out at our [trac|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk] and the [SVN|http://svn.fckeditor.net/FCKeditor.Java/trunk/] directly.
> Checkout the [bin.xml|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk/src/main/assembly/bin.xml] and comment out the first outputFileNameMapping and run "mvn clean site package assembly:assembly".
> You should be able to reproduce the problem.
> I did find a workaround for the problem by defining the outputFileNameMapping as same as in the modules poms. This works just because all modules have the same finalName remapping.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira