Maven 2.x Assembly Plugin

unpack = false does not work

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Cannot Reproduce
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    OS/X 10.4, JDK1.5
  • Number of attachments :
    2

Description

I use the assembly attached to build a distributable version of a Java command line tool. I'd like to have a lib/ directory with the jars the project depends on, so that I may include them via a BASH script.

with unpack = false, I get the error in the attach.

Attachments

  1. XML File
    bin.xml
    16/May/08 8:04 AM
    1 kB
    Marco Brandizi
  2. Text File
    log.txt
    16/May/08 8:04 AM
    330 kB
    Marco Brandizi

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
John Casey added a comment -

can you tell me which operating system you're on? This isn't an error I've ever seen before...it seems like a problem in the tar command itself, like maybe one of the files it's trying to add is messed up somehow.

Show
John Casey added a comment - can you tell me which operating system you're on? This isn't an error I've ever seen before...it seems like a problem in the tar command itself, like maybe one of the files it's trying to add is messed up somehow.
Hide
Permalink
Marco Brandizi added a comment - - edited

I have the envirnoment:

Mac OS/X 10.4.11
tar (GNU tar) 1.14 +CVE-2006-0300 +CVE-2006-6097

java version "1.5.0_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-241)
Java HotSpot(TM) Client VM (build 1.5.0_13-121, mixed mode, sharing)

Maven version: 2.0.8

Yes, should be a problem with packaging. I've tried to remove <format>tar.bz2</format>, leaving zip, but a 'lib' file (not directory) is created. If i do "unzip -l lib" I can see that only one dependent jar is stored in it. It also creates a .zip which is sized 18Mb, so apparently all the jars are poured in it, but when I unzip it I have an empty lib/ directory.

Show
Marco Brandizi added a comment - - edited I have the envirnoment: Mac OS/X 10.4.11 tar (GNU tar) 1.14 +CVE-2006-0300 +CVE-2006-6097 java version "1.5.0_13" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-241) Java HotSpot(TM) Client VM (build 1.5.0_13-121, mixed mode, sharing) Maven version: 2.0.8 Yes, should be a problem with packaging. I've tried to remove <format>tar.bz2</format>, leaving zip, but a 'lib' file (not directory) is created. If i do "unzip -l lib" I can see that only one dependent jar is stored in it. It also creates a .zip which is sized 18Mb, so apparently all the jars are poured in it, but when I unzip it I have an empty lib/ directory.
Hide
Permalink
John Casey added a comment -

Can you attach your assembly descriptor, or a sanitized version of it if it contains sensitive information? I'd like to see how you're using outputDirectory vs. outputFileNameMapping...

It's strange...I use OS X as well, and create tar.bz2, tar.gz, and .zip files all the time...I've never seen this.

Show
John Casey added a comment - Can you attach your assembly descriptor, or a sanitized version of it if it contains sensitive information? I'd like to see how you're using outputDirectory vs. outputFileNameMapping... It's strange...I use OS X as well, and create tar.bz2, tar.gz, and .zip files all the time...I've never seen this.
Hide
Permalink
Marco Brandizi added a comment -

It is attached, is bin.xml.

Show
Marco Brandizi added a comment - It is attached, is bin.xml.
Hide
Permalink
Cestmír Ruzicka added a comment - - edited

outputFileNameMapping is a good thing to change.
see MASSEMBLY-217 for patch.
You don't need this patch, but youll see error message just for you

Show
Cestmír Ruzicka added a comment - - edited outputFileNameMapping is a good thing to change. see MASSEMBLY-217 for patch. You don't need this patch, but youll see error message just for you
Hide
Permalink
Marco Brandizi added a comment -

I've put my hands back on it. By removing outputFileNameMapping it works!

Thanks a lot.

Show
Marco Brandizi added a comment - I've put my hands back on it. By removing outputFileNameMapping it works! Thanks a lot.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.