[ http://issues.apache.org/jira/browse/BEEHIVE-561?page=comments#action_65708 ] Eddie O'Neil commented on BEEHIVE-561: --------------------------------------
There actually *is* a <control-jar> Ant task -- take a look at ControlJarTask. This enhancement would be to add the <control-jar> macro that wraps it so that callers can avoid the taskdef and having to know the classpath needed to create an instance of the task. The ControlJarTask also extends the Ant Jar task, so users can just pass Ant properties. I'm not convinced at this point that we should do this because we'd just end up mirroring the Jar API on the macro, and yes, I filed the enhancement. :) > add a control-jar macro to beehive-tools.xml > -------------------------------------------- > > Key: BEEHIVE-561 > URL: http://issues.apache.org/jira/browse/BEEHIVE-561 > Project: Beehive > Type: Improvement > Components: Controls > Versions: V1Alpha, V1Beta, V1 > Reporter: Eddie O'Neil > Assignee: Bryan Che > Priority: Minor > Fix For: V1 > > To be consistent and to keep a Beehive developer from having to define it for > every control project, Beehive should provide the <control-jar> macro to > abstract the definition of the <control-jar> Ant task. This would ease the > process of creating a JAR for a particular control implementation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
