Ian –
Thanks for the
comments. You make a good point about clean not being discoverable. If
possible, I would like the annotation processors that are only runnable in
batch mode to still be as automatic as is reasonable. A manual “Run APT” or
the like may be our best route for those cases where one does not want to run
a clean before building. We’ll need to investigate that, and see if some of
our more problematic processors can be run from a non-clean
project.
Thanks,
Jess
From:
jdt-apt-dev-bounces@xxxxxxxxxxx [mailto:jdt-apt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Ian
Carr
Sent: Tuesday, August
16, 2005 3:32 AM
To:
jdt-apt-dev@xxxxxxxxxxx
Subject: [jdt-apt-dev] Batch mode
operation
Jess, Just as a general follow up
to my bugzilla comment:
[
https://bugs.eclipse.org/bugs/show_bug.cgi?id=106541 Bug
106541 - ClassLoader problem when generating code with APT ]
Your batch mode, as an optional
alternative launch mechanism, sounds good to me, I can imagine some larger
slower generators becoming painful if run during autobuilds, the ability to
avoid this, whilst retaining the same configuration approach, may become very
useful.
Tying things into the clean
mechanism does not always make for the simplest way to trigger things,
particularly as 'Clean' does not appear on the right click menu for projects.
It can also be pretty time consuming in a large workspace/project.
Perhaps we need a separate
'Generate phase' mechanism for this purpose, maybe with it's own toolbar
button/project menu, tied into tools like yours and also appearing as another
selectable ant task target element in the ant-builder. And (getting even
further off topic) if that were possible a 'Release' phase to run packaging
tasks would be nice.
Hope this helps
Ian Carr
Head of Technical
Architecture
Focus Software ltd