[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
|
[news.eclipse.tools.jdt] Re: apt: Not working in 3.2M6?
|
- From: Jess Garms <jgarms@xxxxxxx>
- Date: Tue, 04 Apr 2006 10:43:01 -0700
- Newsgroups: eclipse.tools.jdt
- Organization: EclipseCorner
- User-agent: Thunderbird 1.5 (Windows/20051201)
Two ideas:
1) I read somewhere in an old message that APT needed to be "activated" per
project. This is not mentioned in introToAPT and I can't find any option to
do it. If necessary, how ?
That's just the checkbox under Project Settings -> Java Compiler ->
Annotation Processing, labeled "Enable annotation processing".
2) I read under "bugs and problems" something about tool.jar that was not
mentioned elsewhere in the document. Is there something I need to do here or
is the comment releated to an old case.
Yes, this is no longer a problem. I'll update the website to reflect this.
In any case, I think APT needs some debugging output so that users (and you
guys) can find out what is wrong?
We do have that:
To do this create a new .options file, say "trace.apt" in the same
directory as eclipse.exe, with the following content (excluding the ***):
***
# Turn on debug tracing for org.eclipse.jdt.core plugin
org.eclipse.jdt.apt.core/debug=true
***
Launch Eclipse with the new options file via:
eclipse -debug trace.apt
And if APT is being dispatched you should see some output. I suspect,
however, that APT is not being called at all. Could you zip up your
project and email it to me directly and I can take a closer look?
Thanks,
Jess Garms