[ http://issues.apache.org/jira/browse/BEEHIVE-374?page=all ]
Chad Schoettger updated BEEHIVE-374:
------------------------------------
Assign To: (was: Chad Schoettger)
After a bit more investigation it appears that Ant has some problems running
Apt when fork is set to false. It appears that Ant will be disabling setting
the fork attribute to false in the near future, (See ASF Bugzilla 33882 for
additional information).
I have been seeing errors when running with fork set to false, here's a sample:
[apt] warning: Bad annotation processor factory: java.lang.ClassCastException:
org.apache.beehive.controls.runtime.generator.apt.ControlAnnotationProcessorFactory
[apt] warning: Bad annotation processor factory:
java.lang.ClassCastException:
org.apache.beehive.controls.runtime.generator.apt.ControlClientAnnotationProcessorFactory
I think the best thing for now is to hold off on fixing this bug until things
settle down in Ant around apt.
> Make <apt> ant task respect the fork attribute
> ----------------------------------------------
>
> Key: BEEHIVE-374
> URL: http://issues.apache.org/jira/browse/BEEHIVE-374
> Project: Beehive
> Type: Improvement
> Components: Controls
> Versions: V1Alpha, 1.1, V1Beta, v1m1, V1
> Reporter: Kyle Marvin
> Attachments: BEEHIVE-374.diff, BEEHIVE-374.zip
>
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
