maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Gier (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MASSEMBLY-282) Fix failing IT no-appendAssemblyId-no-classifier
Date Thu, 14 Feb 2008 00:51:28 GMT

     [ http://jira.codehaus.org/browse/MASSEMBLY-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paul Gier updated MASSEMBLY-282:
--------------------------------

    Attachment: maven-assembly-plugin-AddArtifactTask-improved.patch

I'm attaching what I think is a slightly improved patch.  This one modifies the class AddArtifactTask.
 This catches more scenarios in which the archiver tries to add an archive to itself.

> Fix failing IT no-appendAssemblyId-no-classifier
> ------------------------------------------------
>
>                 Key: MASSEMBLY-282
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-282
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>            Reporter: Paul Gier
>         Attachments: maven-assembly-plugin-AddArtifactTask-improved.patch, maven-assembly-plugin-AddDependencySetsTask.patch
>
>
> The IT no-appendAssemblyId-no-classifier is currently failing.  This is due to the fact
that the dependency set task tries to include the main project artifact as one of the dependencies.
 This causes a problem when there is no assembly ID and no classifier, because the archiver
tries to include the destination file for the assembly in itself.
> The patch adds a check to make sure the archiver destination file does not get included
as one of the entries.  The patch also includes updates to the unit tests to reflect the new
behaviour of the AddDependencySetsTask.

-- 
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

        

Mime
View raw message