[
https://jira.codehaus.org/browse/MASSEMBLY-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329504#comment-329504
]
Wolfgang Grossinger commented on MASSEMBLY-660:
-----------------------------------------------
During the creation of the test project, I found the bug, so you can close the
ticket.
The problem was, that during the step to deploy the .jar + config files, the
config is filtered to prepare it for the correct environment where it is
deployed to. This also included the .pdf, what was wrong.
Maybe you can open another issue for resource filtering, because manipulating
.pdf - Files during resource filtering seems to be quite crazy to me...
Thank's for the great test case, I'm not sure if/when I would have found the
mistake without you :-)
> Creating a Zip doesn't work correctly
> -------------------------------------
>
> Key: MASSEMBLY-660
> URL: https://jira.codehaus.org/browse/MASSEMBLY-660
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: Windows 7 64 Bit
> Reporter: Wolfgang Grossinger
> Attachments: ZPS ProtocolUploader Handbuch.pdf
>
>
> We have a simple batch that is deployed in 2 Parts to Nexus: the .jar itself
> and a .zip with configuration information which also includes the attached
> .pdf.
> After the deployment to Nexus, everything is correct so far (we can still
> open the .pdf and the content is ok).
> When we deploy the Batch to our Host-System, we load the dependencies from
> Nexus, unpack them, prepare the config files for the according
> Host-Environment and repack all again as a .zip-File.
> - Unpackaging seems to be ok, we can still open the .pdf and read the
> contents, but after repackaging the files, the .pdf is broken (the size is
> still the same, we can open it but it is no longer possible to display the
> content as it seems that one bit or so has changed.
> - We checked also our Zip-Programs to be sure it is not because of a bug in
> one of the programs but neither 7zip nor the Windows built in program was
> able to produce a correct result.
> -> this may not be a direct problem of the assembly plugin but of some libs,
> the plugin uses. As we don't know which libs you use we just can report the
> problem here, you may be able to switch to a newer lib or report the bug to
> the right people :-)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
