[jira] (MASSEMBLY-624) Multiple attachments with reused assembly descriptor - classifier for attach should be configurable in maven-assembly-plugin execution configuration

["Sven Ludwig (JIRA)" <ji...@codehaus.org>]

Sven Ludwig created MASSEMBLY-624:
-------------------------------------

             Summary: Multiple attachments with reused assembly descriptor - classifier for attach should be configurable in maven-assembly-plugin execution configuration
                 Key: MASSEMBLY-624
                 URL: https://jira.codehaus.org/browse/MASSEMBLY-624
             Project: Maven 2.x Assembly Plugin
          Issue Type: Improvement
    Affects Versions: 2.3
            Reporter: Sven Ludwig


It should be possible to create multiple assembly products with different classifiers using only one assembly-descriptor.

Currently, the configuration property classifier is deprecated (and apparently also not honored), and instead, the assembly ID is used as the classifier.

I suggest to reactivate the classifier property in a way that it becomes possible to define the classifier within the configuration of an execution and thus multiple assembly products may be attached using only one reused assembly-descriptor.


More about the problem:

If there is more than one execution with attach true, there will be the warning message artifact 2already attached to project, ignoring duplicate".

See:

http://stackoverflow.com/questions/8734706/maven-assembly-plugin-uploading-the-right-zip-file
Citation: "Even if you have given the zips different finalName values, they still inherit the classifier from the ID in the assembly descriptor."

http://stackoverflow.com/questions/1326527/maven-assembly-plugin-custom-jar-filenames
(answer by Rich Seller, scroll down a bit)

Note that it is not possible to have a variing assembly ID for one assembly-descriptor inside a pom.xml (e.g. it is not possibly to define the assembly ID as a property that has a different value for each execution).





--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira