| Annotation processing configuration [message #260574] |
Thu, 11 June 2009 13:45  |
Eclipse User |
|
|
|
Hi guys,
We're using BEA Workshop 10.0.1 (based on Eclipse 3.2) as our IDE and
we're experiencing painfully long compile times, somewhere around 10
minutes. After some research, we've found that we're experiencing the
same problems with our Ant build, and in this case the culprit is clearly
the annotation manifest generation: it seems to be processing not only our
compiled classes but also all classpath libraries, which takes a lot of
time. The generate manifest Ant task can be configured to scan only
specific file sets, but I can't seem to find something similar in Eclipse.
Any idea anyone?
Thanks,
GB
|
|
|
| Re: Annotation processing configuration [message #260596 is a reply to message #260574] |
Sat, 13 June 2009 01:51  |
| Eclipse User |
|
|
|
"Guillaume Bilodeau" <gbilodeau@yahoo.com> wrote in message
news:77e7f5385b5ddb4693b0297c47776dbf$1@www.eclipse.org...
> Hi guys,
>
> We're using BEA Workshop 10.0.1 (based on Eclipse 3.2) as our IDE and
> we're experiencing painfully long compile times, somewhere around 10
> minutes. After some research, we've found that we're experiencing the
> same problems with our Ant build, and in this case the culprit is clearly
> the annotation manifest generation: it seems to be processing not only our
> compiled classes but also all classpath libraries, which takes a lot of
> time. The generate manifest Ant task can be configured to scan only
> specific file sets, but I can't seem to find something similar in Eclipse.
>
> Any idea anyone?
See if you can reduce the size of the jars on your classpath... also, if
you can upgrade to a newer version of Workshop, I think 10.3 was based on
Eclipse 3.3? If I recall correctly there were some perf improvements that
went into that.
I don't know of any other way to restrict the set of things that APT has to
inspect, within the IDE, at this point. It should not be processing your
libraries (in the sense of searching for annotations within them), but it is
possible that one of the annotation processors is querying the typesystem
for information that requires searching every package fragment every time.
As I said, I think BEA did some perf improvements in later versions of the
annotation processors, and there have also been some perf improvements in
the APT implementation in Eclipse (though more certainly remains to be
done).
|
|
|
Powered by
FUDForum. Page generated in 0.08109 seconds
Home