maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Casey (JIRA)" <>
Subject [jira] Closed: (MASSEMBLY-282) Fix failing IT no-appendAssemblyId-no-classifier
Date Thu, 14 Feb 2008 21:18:28 GMT


John Casey closed MASSEMBLY-282.

    Resolution: Fixed

I modified the patch to copy the conflicting file to a temporary location then include it
from there, rather than skipping it entirely. This supports the use case where the assembly
plugin is used to post-process the output artifact for a build, but that post-processing is
meant to include the main artifact's contents.

> Fix failing IT no-appendAssemblyId-no-classifier
> ------------------------------------------------
>                 Key: MASSEMBLY-282
>                 URL:
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>            Reporter: Paul Gier
>            Assignee: John Casey
>             Fix For: 2.2-beta-2
>         Attachments: maven-assembly-plugin-AddArtifactTask-improved.patch, maven-assembly-plugin-AddDependencySetsTask.patch
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
> 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:
For more information on JIRA, see:


View raw message