Unfortunately the assembly plugin doesn't understand the concept of classifiers at the moment. There are numerous bugs open on the issue - please vote on them if you haven't done so yet.
I've solved the problem using a dependency plugin to copy the dependencies with classifiers to a target location, then using assembly's fileset on them. Kalle On 11/2/07, jpanelli <[EMAIL PROTECTED]> wrote: > > > We have some dependencies that have a secondary artifact with a classifier > called "conf-resources". The secondary artifact is a zip that contains > binary files that we want to include in an assembly. We can include the > secondary artifact in the assembly when it is a module with this assmbly > descriptor: > > <moduleSet> > <includes> > <include>*:smar:*</include> > </includes> > <binaries> > <attachmentClassifier>conf-resources</attachmentClassifier> > <includeDependencies>true</includeDependencies> > <unpack>true</unpack> > <outputFileNameMapping>local</outputFileNameMapping> > </binaries> > </moduleSet> > > However, when the secondary artifact is in attached to a dependency, there > is no <attachmentClassifier> tag inside of <dependencySet>, so we can not > figure out how to structure the assembly descriptor to include it in the > assembly. We've tried numerous things. Is it even possible to do this? > -- > View this message in context: > http://www.nabble.com/How-do-I-get-secondary-artifacts-of-dependencies-into-an-assembly--tf4741283s177.html#a13558032 > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
