[ http://issues.apache.org/jira/browse/BEEHIVE-561?page=all ]
Bryan Che updated BEEHIVE-561:
------------------------------
Fix Version: V1
(was: TBD)
I'll put this in V1. But, it seems to me that creating a control-jar task
rather than macro would be better. There isn't much to abstract out, and
keeping it a task lets users customize their jars better via jar task options.
Thoughts?
> 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: V1, V1Alpha, V1Beta
> 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
