You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Ashley Williams <as...@db.com> on 2008/01/30 11:04:23 UTC
Odd behaviour of maven resources plugin
Hi,
I'm trying to use the resources plugin in order to filter the out of the
box jboss, as I wish to rename the 'all' server to a different name and
also strip out unused parts. So naturally I've added a configuration to
the pom.xml as follows:
<resource>
<!-- just the jboss application without servers -->
<directory>${basedir}/src/main/jboss-eap-4.2</directory>
<excludes>
<exclude>server/all/**/*</exclude>
<exclude>jar-versions.xml</exclude>
</excludes>
<targetPath>template/CUSTOM_JBOSS</targetPath>
</resource>
<resource>
<!-- use the jboss all server (without unused components) but
rename to custom -->
<directory>
${basedir}/src/main/jboss-eap-4.2/server/all
</directory>
<excludes>
<exclude>**/hibernate*.jar</exclude>
<exclude>**/jbossmq*.jar</exclude>
<exclude>**/jboss-messaging*.jar</exclude>
<exclude>**/jboss-remoting*.jar</exclude>
<exclude>deploy/jms/**/*</exclude>
<exclude>deploy-hasingleton/jms/**/*</exclude>
<exclude>farm/**/*</exclude>
</excludes>
<targetPath>template/JBOSS/server/custom</targetPath>
</resource>
About 20% of the time I the resources I'm trying to filter end up in the
target jboss directory anyway, as if the filter rules are completely
ignored. Can anyone shed any light on this?
Thanks
- Ashley
---
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.