| APT and jdt.compiler.tool plugins [message #247869] |
Wed, 19 September 2007 12:12  |
Eclipse User |
|
|
|
Originally posted by: eclipse5.rizzoweb.com
In the course of working on an Eclipse-based tool, I've noticed that our
debug runtime is complaining that it can't resolve a few of the JDT
bundles related to APT and compiler.tool. I'm pretty sure the reason is
that those plugins require a J2SE-16. execution environment but our tool
is designed to run under 1.5.
My question is, what, if anything, will we be missing out on by not
supporting those plugins? I reviewed some info on the APT home page, but
I would like to know if all annotation processing functionality in
Eclipse essentially requires 1.6 or not.
Similarly, it appears that the jdt.compiler.tool plugin is related to
JSR 199 support, but I don't really know what functionality in Eclipse
that maps to. Any insight about that is appreciated, too.
TIA,
Eric
|
|
|
| Re: APT and jdt.compiler.tool plugins [message #247900 is a reply to message #247869] |
Wed, 19 September 2007 14:49  |
| Eclipse User |
|
|
|
Eric Rizzo a écrit :
> In the course of working on an Eclipse-based tool, I've noticed that our
> debug runtime is complaining that it can't resolve a few of the JDT
> bundles related to APT and compiler.tool. I'm pretty sure the reason is
> that those plugins require a J2SE-16. execution environment but our tool
> is designed to run under 1.5.
> My question is, what, if anything, will we be missing out on by not
> supporting those plugins? I reviewed some info on the APT home page, but
> I would like to know if all annotation processing functionality in
> Eclipse essentially requires 1.6 or not.
If you are using 1.5, you should be able to use the IDE APT5 support.
The ones that require 1.6 are specific for the APT6 support. This
includes the apt support inside the batch compiler.
> Similarly, it appears that the jdt.compiler.tool plugin is related to
> JSR 199 support, but I don't really know what functionality in Eclipse
> that maps to. Any insight about that is appreciated, too.
The jsr199 support is used if you are using 1.6 code and you want to be
able to compile java code programmatically.
So from the IDE itself, it is not used. These classes however are
present in the ecj-XXX.jar available with every eclipse build, where XXX
is the build ID.
This allows users to simply add this jar on their classpath to use the
Eclipse compiler inside ant task, jsr199 calls or apt processing.
HTH,
--
Olivier
|
|
|
| Re: APT and jdt.compiler.tool plugins [message #247904 is a reply to message #247869] |
Wed, 19 September 2007 15:29 |
| Eclipse User |
|
|
|
Originally posted by: wharley.bea.com
"Eric Rizzo" <eclipse5@rizzoweb.com> wrote in message
news:fcrhpf$eai$1@build.eclipse.org...
> In the course of working on an Eclipse-based tool, I've noticed that our
> debug runtime is complaining that it can't resolve a few of the JDT
> bundles related to APT and compiler.tool. I'm pretty sure the reason is
> that those plugins require a J2SE-16. execution environment but our tool
> is designed to run under 1.5.
> My question is, what, if anything, will we be missing out on by not
> supporting those plugins? I reviewed some info on the APT home page, but I
> would like to know if all annotation processing functionality in Eclipse
> essentially requires 1.6 or not.
Olivier's answered the JSR-199 question; I'll address APT.
The Java 5 annotation processing functionality (processors written to the
com.sun.mirror.apt API) only requires a 1.5 VM, and the
org.eclipse.jdt.apt.core and ...apt.ui plug-ins.
The Java 6 annotation processing functionality (processors written to the
javax.annotation.processing API) requires a 1.6 VM, and the
org.eclipse.jdt.apt.pluggable.core and org.eclipse.jdt.compiler.apt plug-ins
as well as the other org.eclipse.jdt.apt.* plug-ins.
So, if you're not using Java 6 processors, you don't need a 1.6 VM, at least
with regard to APT. You can ignore the "plug-in not loaded" warnings.
|
|
|
| Re: APT and jdt.compiler.tool plugins [message #247919 is a reply to message #247904] |
Wed, 19 September 2007 22:09 |
| Eclipse User |
|
|
|
Originally posted by: eclipse5.rizzoweb.com
Walter Harley wrote:
> "Eric Rizzo" <eclipse5@rizzoweb.com> wrote in message
> news:fcrhpf$eai$1@build.eclipse.org...
>> In the course of working on an Eclipse-based tool, I've noticed that our
>> debug runtime is complaining that it can't resolve a few of the JDT
>> bundles related to APT and compiler.tool. I'm pretty sure the reason is
>> that those plugins require a J2SE-16. execution environment but our tool
>> is designed to run under 1.5.
>> My question is, what, if anything, will we be missing out on by not
>> supporting those plugins? I reviewed some info on the APT home page, but I
>> would like to know if all annotation processing functionality in Eclipse
>> essentially requires 1.6 or not.
>
> Olivier's answered the JSR-199 question; I'll address APT.
>
> The Java 5 annotation processing functionality (processors written to the
> com.sun.mirror.apt API) only requires a 1.5 VM, and the
> org.eclipse.jdt.apt.core and ...apt.ui plug-ins.
>
> The Java 6 annotation processing functionality (processors written to the
> javax.annotation.processing API) requires a 1.6 VM, and the
> org.eclipse.jdt.apt.pluggable.core and org.eclipse.jdt.compiler.apt plug-ins
> as well as the other org.eclipse.jdt.apt.* plug-ins.
>
> So, if you're not using Java 6 processors, you don't need a 1.6 VM, at least
> with regard to APT. You can ignore the "plug-in not loaded" warnings.
Thanks guys - those were both answers that I was hoping to hear.
Eric
|
|
|
Powered by
FUDForum. Page generated in 0.09717 seconds
Home