[ 
https://jira.codehaus.org/browse/MASSEMBLY-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298745#comment-298745
 ] 

Christoph Gritschenberger commented on MASSEMBLY-557:
-----------------------------------------------------

I'm not sure that's it.
We do not use either <dependencySet> nor <unzip> in our assembly-descriptor.
The "config" directory in question, is part of the assembly's src-folder (--> 
it's copied from target/classes).

We basically unpack another assembly (apache-karaf) and among other things add 
an additional folder named "config".
The unpacking we configured using an execution-configuration in the assembly's 
pom.xml

{code}
<plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-dependency-plugin</artifactId>
        <executions>
          <execution>
            <id>unpack-unix</id>
            <phase>generate-resources</phase>
            <goals>
              <goal>unpack</goal>
            </goals>
            <configuration>
              <artifactItems>
                <artifactItem>
                  <groupId>org.apache.karaf</groupId>
                  <artifactId>apache-karaf</artifactId>
                  <type>tar.gz</type>
                  <outputDirectory>target/dependencies/unix</outputDirectory>
                </artifactItem>
              </artifactItems>
            </configuration>
          </execution>
          ...
{code}

The config-directory is added using a <fileSet>
{code}
    ...
    <fileSet>
      <directory>target/classes/config</directory>
      <outputDirectory>/config/</outputDirectory>
      <lineEnding>dos</lineEnding>
      <fileMode>0644</fileMode>
    </fileSet>
    ...
{code}

                
> Corrupted zip created by assembly: extracting the zip forgets certain folders 
> (or throws permission denied errors) possibly because zip index is corrupted
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-557
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-557
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2.1
>            Reporter: Geoffrey De Smet
>            Priority: Critical
>         Attachments: 
> droolsjbpm-integration-distribution-5.2.0.M2_BROKEN_IN_reference_manual_gutted.zip
>
>
> Take a look at the attached zip created by the assembly plugin.
> - If you open it, you can see navigate to the submap 
> /droolsjbpm-integration-distribution-5.2.0.M2/reference_manual/pdf/. In that 
> map you find the file droolsjbpm-integration-docs.pdf which you can open with 
> a PDF reader.
> - If instead you extract the entire archive to a directory, and navigate to 
> the submap 
> /droolsjbpm-integration-distribution-5.2.0.M2/reference_manual/pdf/, you 'll 
> find that that map is unreadable (chmod 000) and the pdf file is gone.
> The directories html_single and html suffer the same fate, but none of the 
> other directories do.
> I used the default linux Ubuntu 10.10 archive manager (which according to 
> about screen is called "File-roller 2.32.0").
> I used Maven 3.0.3, maven-assembly-plugin 2.2.1.
> Note that that attached zip is gutted to stay inside the maximum file upload 
> size.
> Possible reproduce recipe:
> {code}
> git clone g...@github.com:droolsjbpm/droolsjbpm-integration.git
> cd droolsjbpm-integration
> git checkout 5.2.0.M2
> mvn clean install -DskipTests -Dfull
> cd droolsjbpm-integration/target
> ls
> {code}
> {code}
> checkdir error:  cannot create 
> /home/gdesmet/tmp/releases/problem_with_the_release_zip/droolsjbpm-integration-distribution-5.2.0.M2/reference_manual/html_single/images
>                  Permission denied
>                  unable to process 
> droolsjbpm-integration-distribution-5.2.0.M2/reference_manual/html_single/images/.
> ...
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to