[
http://jira.codehaus.org/browse/MASSEMBLY-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MASSEMBLY-282:
---------------------------------
Assignee: John Casey
Description:
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.
was:
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.
Fix Version/s: 2.2-beta-2
Remaining Estimate: 0 minutes
Original Estimate: 0 minutes
> 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
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
