Mine now looks like the following, and the last three excludes are
ineffectual in excluding.
<dependencySets>
<dependencySet>
<outputDirectory>lib</outputDirectory>
<unpack>false</unpack>
<scope>compile</scope>
<excludes>
<exclude>org.springframework:*</exclude>
<exclude>com.basistech.rlpj:rlp-bl-lucene2.4</exclude>
<exclude>com.basistech.rlpj:rlp-common</exclude>
<exclude>com.basistech.rlpj:dictionaries</exclude>
</excludes>
</dependencySet>
</dependencySets>
On Wed, Jul 15, 2009 at 4:14 PM, David C. Hicks<[email protected]> wrote:
> This is an excerpt from my assembly.xml. It uses the Maven style
> descriptors for inclusion. Versions are assumed to be those referenced
> by the module (or in dependency management).
>
> <dependencySets>
> <dependencySet>
> <includes>
> <include>com.allureglobal:salient-war</include>
> <include>com.allureglobal:salient-database-schema</include>
> <include>com.allureglobal:salient-web-services</include>
> <include>mysql:mysql-connector-java</include>
> <include>org.liquibase:liquibase-core</include>
> </includes>
> </dependencySet>
> </dependencySets>
>
>
> Benson Margulies wrote:
>> This page:
>> http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/including-and-excluding-artifacts.html
>>
>> talks about group:artifact:classifier:version
>>
>> but all the examples I can find seem to be just filtering filenames.
>>
>> Are both formats supposed to work?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
