[ http://jira.codehaus.org/browse/MJAR-30?page=comments#action_70675 ] Simon Kitching commented on MJAR-30: ------------------------------------
I'd also like to see include/exclude for the jar plugin. Like the original requester, I have a project (jakarta commons logging) where three jars are created: one with the full set of classes, and two with selected subsets. All three need to be created to build a "distribution". Splitting into separate modules doesn't seem right to me; this is the same codebase with exactly the same classes, unit tests, etc. It's more like the "classifier" concept. Rebinding maven-jar-plugin using executions with different include/exclude patterns configured would seem to be a perfectly fine solution to this problem. And besides, there is an ant build already in place, so restructuring the source code (breaking the ant build) just for the purposes of creating maven modules isn't tempting. I'll try to create a patch, though for someone already familiar with maven plugins this would be a lot quicker! Thanks, Simon > Allow inludes/excludes definition > --------------------------------- > > Key: MJAR-30 > URL: http://jira.codehaus.org/browse/MJAR-30 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement > Reporter: Michael Böckling > > Allow the definition of includes / excludes, so the Jars content can be > customized. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
