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 23:09:26 UTC

[jira] Created: (MASSEMBLY-339) Overridden artifact finalName with classifier is ignored by the assembly plugin.

Overridden artifact finalName with classifier is ignored by the assembly plugin.
--------------------------------------------------------------------------------

                 Key: MASSEMBLY-339
                 URL: http://jira.codehaus.org/browse/MASSEMBLY-339
             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: assemblyClassifierMapping.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 javadoc jars but their names do not correspond to the overridden finalNames.
The javadoc:jar genereation is bound to the package phase.

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 second 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-339) Overridden artifact finalName with classifier is ignored by the assembly plugin.

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MASSEMBLY-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg updated MASSEMBLY-339:
--------------------------------------

    Fix Version/s:     (was: 2.2)

> Overridden artifact finalName with classifier is ignored by the assembly plugin.
> --------------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-339
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-339
>             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: assemblyClassifierMapping.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 javadoc jars but their names do not correspond to the overridden finalNames.
> The javadoc:jar genereation is bound to the package phase.
> 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 second 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-339) Overridden artifact finalName with classifier is ignored by the assembly plugin.

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MASSEMBLY-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey closed MASSEMBLY-339.
--------------------------------

       Resolution: Won't Fix
    Fix Version/s: 2.2-beta-6
         Assignee: John Casey

See fix in MASSEMBLY-338, but maybe try adding ${dashClassifier?} to the expression:

${artifact.build.finalName}-${artifact.version}${dashClassifier?}.${artifact.extension}

> Overridden artifact finalName with classifier is ignored by the assembly plugin.
> --------------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-339
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-339
>             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: assemblyClassifierMapping.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 javadoc jars but their names do not correspond to the overridden finalNames.
> The javadoc:jar genereation is bound to the package phase.
> 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 second 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