I'm planning to fix this in the next release, just haven't done it yet. I'm
not entirely sure whether it's been documented in JIRA, but I do think it's
there...
http://jira.codehaus.org/browse/MASSEMBLY
-john
On 5/11/07, Lacoste, Dana [EMAIL PROTECTED] wrote:
I asked this a month ago (and
On 5/5/07, Marshall Schor [EMAIL PROTECTED] wrote:
snip/
However, if the same XML is used with Maven 2.0.6, an extra directory
is created having the name of the packed zip source:
root / eclipsePlugins / uimaj-ep-debug-2.1.0-incubating.zip /
org.apache.uima.debug.2.1.0.incubating / etc.
I reported this to Mevenide and should be fixed in future versions. A work
around is to lock down the assembly version you are using:
...
plugin
artifactIdmaven-assembly-plugin/artifactId
version2.1/version
I asked this a month ago (and was told the quick answer then) so I'll
give the quick answer now.
To avoid the adding a level of directories when building an assembly
with unpack, add this to your assembly .xml (not the pom) when unpacking
the dependency:
outputFileNameMapping/
this will say
This issue seems perhaps not related to Maven levels - but is caused by
something else - because other 2.0.6 tooling seems to work. Will
investigate further...
-Marshall
Marshall Schor wrote:
When running with Maven, 2.0.4, the following assembly XML works OK,
but generates wrong output
When running with Maven, 2.0.4, the following assembly XML works OK, but
generates wrong output in Maven 2.0.6:
assembly
idbin/id
formats
formattar.gz/format
formattar.bz2/format
formatzip/format
/formats
includeBaseDirectoryfalse/includeBaseDirectory
!-- This tag is only
