As I mentioned at JbossWorld, I was able implement this using zipfileset.
| <artifactdef artifact="log4j-boot.jar"> | <include input="log4j.jar"> | <include pattern="org/apache/log4j/*"/> | <include pattern="org/apache/log4j/config/*"/> | <include pattern="org/apache/log4j/helpers/*"/> | <include pattern="org/apache/log4j/or/*"/> | <include pattern="org/apache/log4j/spi/*"/> | </include> | </artifactdef> | becomes: | <zipfileset src="C:\projects\jboss-head\thirdparty\apache-log4j\lib\log4j.jar"> | <include name="org/apache/log4j/*"/> | <include name="org/apache/log4j/config/*"/> | <include name="org/apache/log4j/helpers/*"/> | <include name="org/apache/log4j/or/*"/> | <include name="org/apache/log4j/spi/*"/> | </zipfileset> | | It is incremental, based on the timestamps of the files *in* log4j-boot.jar. It also seems quite performant when it does run-- no need for bypass testing. If you include a jar as input, but add no include (or exclude) subelements, the entire jar will be added to the archive -- unexploded. One thing zipfilset also gives us is the prefix attribute, which will be useful for doing things like wars when I get to them. See http://jira.jboss.com/jira/browse/JBBUILD-19 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869235#3869235 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869235 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
