[
http://jira.codehaus.org/browse/MASSEMBLY-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157594#action_157594
]
John Casey commented on MASSEMBLY-285:
--------------------------------------
default behavior is set to skip. Because of the way archive resources are
processed, implementing overwrite is going to be a lot more involved. From the
perspective of the assembly plugin, overwrite vs. skip doesn't make much
difference, since users cannot control which type of assembly section is
processed first, and any of them could overwrite entries from any other. Having
duplicate files that are different will lead to non-deterministic results as
long as you're not talking about any two specific sections, or entries within a
single section, so there is no difference in the general case between skip and
overwrite.
In terms of two fileSets, however, it makes sense to allow overwrites. Since
this is pretty complex to implement in plexus-archiver, I'll create a new issue
for it and assign it to 2.2 (final).
> regression: duplicate files added to the assembly
> -------------------------------------------------
>
> Key: MASSEMBLY-285
> URL: http://jira.codehaus.org/browse/MASSEMBLY-285
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Reporter: Brett Porter
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.2-beta-3
>
>
> I found that it was possible to add a file twice to the assembly through
> different filesets (a zip file) so that when it extracted it prompted for
> overwrite.
> It should error out or collapse the entries (as 2.1 did).
--
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
