beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chad Schoettger (JIRA)" <>
Subject [jira] Updated: (BEEHIVE-374) Make <apt> ant task respect the fork attribute
Date Fri, 07 Oct 2005 15:08:02 GMT
     [ ]

Chad Schoettger updated BEEHIVE-374:


I have created a new class, org.apache.beehive.controls.runtime.generator.AptCompilerAdapter,
to support invoking the APT compiler in-process.  The AptTask has also been modified.   The
default behavior of the AptTask will remain the same (still fork the APT process) unless the
task's fork attribute has been explicitly set to 'no' in the ant build file.  

To apply patch:

    - the file contains the new class 'AptCompilerAdapter' which should be
extracted to: 

    - apply the BEEHIVE-374.diff file as a patch, will patch the AptTask with the necessary
changes to enable in-process invocation of the APT compiler.

> Make <apt> ant task respect the fork attribute
> ----------------------------------------------
>          Key: BEEHIVE-374
>          URL:
>      Project: Beehive
>         Type: Improvement
>   Components: Controls
>     Versions: V1Alpha
>     Reporter: Kyle Marvin
>     Assignee: Chad Schoettger
>  Attachments: BEEHIVE-374.diff,
> The <apt> ant task is built on top of the built-in <javac> task, which includes
a "fork" attribute enabling in-proc invocation of the compiler.   Currently, the apt task
ignores this attribute and will always launch the apt executable in a seperate process.
> The Javac ant task has a pluggable architecture for invoking different compilers and
already has support built in for the various jdk compilers, jikes, sj, etc.
> I think doing this would only involve writing one of these CompilerAdaptor classes for
in-proc APT invocations, then modifying AptTask to configure it.
> Sample compiler adaptors can be found in the ant source distribution under src/main/org/apache/tools/ant/taskdefs/compilers.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message