It turns out that the extra dir was in fact pirate error. But for the excludes I've followed your advice.
On Mon, Nov 15, 2010 at 1:16 PM, Jon Paynter <[email protected]> wrote: > On Mon, Nov 15, 2010 at 6:54 AM, Benson Margulies > <[email protected]>wrote: > >> From the following spec, I get two behaviors that I need to fix >> somehow: (1) I get an extra level of directory named after the >> artifact in spite of the empty outputDirectory element. (2) the >> excludes are apparently completely ignored. Can anyone assist? >> >> <plugin> >> <groupId>org.apache.maven.plugins</groupId> >> <artifactId>maven-dependency-plugin</artifactId> >> <executions> >> <execution> >> <id>unpack-wrapper</id> >> <phase>package</phase> >> <goals> >> <goal>unpack</goal> >> </goals> >> <configuration> >> >> <outputDirectory>${project.build.directory}/wrapper</outputDirectory> >> <artifactItems> >> <artifactItem> >> <groupId>tanuki</groupId> >> >> <artifactId>wrapper-delta-pack-standard</artifactId> >> <version>3.5.6</version> >> <type>tar.gz</type> >> <outputDirectory/> >> >> <excludes>**/bin/DemoApp.bat,**/bin/GetHostId.bat,**/bin/*Test*,**/bin/demoapp/bin/testwrapper,conf/*,**/jdoc,**/jdoc.tar.gz,**/lib/wrapperdemo.jar,**/lib/wrappertest.jar,**/src/conf</excludes> >> </artifactItem> >> </artifactItems> >> </configuration> >> </execution> >> </executions> >> </plugin> >> > > I found the <excludes> and <includes> tags to be useless, so I went and > listed each artifact ID individually when doing an unpack. > > Also, see if its possible to create your initial tar.gz file so the stuff > you want to include is already excluded -- then you wont have to try and > exclude anything. >
