DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6339>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6339 PatternSet Behavior Summary: PatternSet Behavior Product: Ant Version: 1.4.1 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Writing my build scripts I often wish I could just specify the pattern in a PatternSet without the exclude/include attached to the PatternSet element. Example Scenario: A build script must compile classes and produce three jar files. Jar file 1 contains just EJB interfaces (Home and Remote). Jar file 2 contains all EJB classes (Home, Remote and Impl). Jar file 3 contains all supporting classes (common packages utilized by potential EJB clients as well as the EJBs themselves). In the above scenario, one could create three pattern sets. PatternSet 1 includes all EJB interfaces. PatternSet 2 includes all EJB classes. PatternSet 3 contains all other classes not included in PatternSets 1 and 2. It would be easier to do (and require less maintainance) to do it with 2 PatternSets. PatternSet 1 specifies EJB interfaces. PatternSet 2 specifies EJB Impl classes. A task can then use combinations of PatternSet 1 and PatternSet 2 to create all three jars. Example: <patternset id="interfaces"> <pattern name="**/ejb/MyEJBHome.class"/> <pattern name="**/ejb/MyEJB.class"/> </patternset> <patternset id="impl"> <pattern name="**/ejb/MyEJBImpl.class"/> </patternset> <target name="ejbjar"> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
