This is definitely a thread for the users' list, not the dev list.
Having said that, the assembly plugin doesn't currently support wildcards in the dependencySet includes/excludes, for one thing. For another, those includes and excludes (in the dependencySet) are meant to refer to the artifacts by groupId and artifactId using the format 'groupId:artifactId'. -john On 5/23/06, Tim Kettler <[EMAIL PROTECTED]> wrote:
I have not used the assembly plugin further than creating a 'jar-with-dependencies'. You should move this thread to the users list. The audience that can help is probably greater there than on the dev list. -Tim Carsten Karkola schrieb: > What I tried to do is, to filter dependencies and unpack some of them, simply copy others to > some dirs, like: > 1. two dependencies with type zip > <dependencySet> > <outputDirectory>/lib</outputDirectory> > <unpack>true</unpack> > <scope>runtime</scope> > <includes> > <include>*.zip</include> > </includes> > </dependencySet> > 2. a jar > <dependencySet> > <outputDirectory>/</outputDirectory> > <unpack>false</unpack> > <scope>runtime</scope> > <includes> > <include>mymodule*.jar</include> > </includes> > </dependencySet> > 3. another jar > <dependencySet> > <outputDirectory>/</outputDirectory> > <unpack>true</unpack> > <scope>runtime</scope> > <includes> > <include>server*.jar</include> > </includes> > </dependencySet> > > If I change something in the dependencySets-Element, all dependencies will be ignored. > What am I missing here? > > regards, carsten > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
