[ http://jira.jboss.com/jira/browse/JBBUILD-19?page=history ]
Ryan Campbell updated JBBUILD-19: --------------------------------- Description: In the system module there is a need to unjar getopt & log4j and recombine them into other artifacts. This is also done in security and perhaps in aspects. It seems like we should support this as a first-class construct. They could then be included in an artifact like this: <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> was: In the system module there is a need to unjar getopt & log4j and recombine them into other artifacts. This is also done in security and perhaps in aspects. It seems like we should support this as a first-class construct. So this is another source, just like src/main or a resource: <source-artifact id="log4j.jar"/> which extracts the jar contents to output/log4j.jar/* . They could then be included in an artifact like any compiled class: <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> > Allow JARS to act as Sources > ---------------------------- > > Key: JBBUILD-19 > URL: http://jira.jboss.com/jira/browse/JBBUILD-19 > Project: JBoss Build System > Type: Feature Request > Reporter: Ryan Campbell > Assignee: Ryan Campbell > Priority: Critical > Fix For: Q105 > > Original Estimate: 1 day > Remaining: 1 day > > In the system module there is a need to unjar getopt & log4j and recombine > them into other artifacts. This is also done in security and perhaps in > aspects. It seems like we should support this as a first-class construct. > They could then be included in an artifact like this: > <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> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- 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