[
http://issues.apache.org/jira/browse/BEEHIVE-561?page=comments#action_65755 ]
Bryan Che commented on BEEHIVE-561:
-----------------------------------
Right, I also want to avoid mirroring the Jar API on a macro. So, I'm
proposing that we add
<taskdef name="control-jar"
classname="org.apache.beehive.controls.runtime.packaging.ControlJarTask"
classpathref="controls.dependency.path" onerror="report" />
to beehive-tools.xml (and remove the repeated declarations elsewhere). This
will still save developers the work of having to repeatedly define the taskdef
since they can just import beehive-tools.xml, but it will allow them to use the
control-jar task as they currently are doing.
> 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
