Re: [jdt-core-dev] Apt processor handling

[Stefan Xenos <sxenos@xxxxxxxxxx>]

I'm also very interested in APT. Reworking the APT system has been on my bucket list for awhile but I can't spend any time on it until the new index is under control.

One of my key pain points has been the effort involved in setting up Eclipse for debugging annotation processors. Currently, you need to create a plugin project and overload an extension point to get Eclipse to open the debugger on your annotation processor, which is very inconvenient. I've never actually gotten it to work.

> all annotation processors work on all project sources

This is a critical issue for some of my users. I get a lot of requests to be able to use different annotation processors that handle the @Inject annotations in different parts of the same project.

  - Stefan

On Thu, Sep 29, 2016 at 10:33 AM Daniel Megert <daniel_megert@xxxxxxxxxx> wrote:

Hi Lars

> Are there plans to improve this? Without knowing the technical details
> here, maybe a "Search in project classpath" option could be added?

Is there a corresponding bug for this?

Our focus is Java 9 and APT has low priority. I know that Sergey is interested in improvements in the area of APT.

Dani



From:        Lars Vogel <lars.vogel@xxxxxxxxxxx>
To:        "Eclipse JDT Core developers list." <jdt-core-dev@xxxxxxxxxxx>
Date:        29.09.2016 13:58
Subject:        [jdt-core-dev] Apt processor handling
Sent by:        jdt-core-dev-bounces@xxxxxxxxxxx

---

Dear JDT core developers,

A fellow Java champion pointed out to me that the annotation
processing setup in Eclipse is very complex compared to other IDEs.
Here is what we wrote me (slightly reworked for readability):

QUOTE_BEGIN
------------
- NetBeans automatically finds APT JARs in the classpath. You can't
turn it off. You can't tweak any settings.
- IntelliJ  allows to activate APT processing (per project) with a
checkbox; this will find all available APT JARs in the classpath by
default. You can also configure which JARs may be used.
- Eclipse forces you to locate and define every APT JAR by hand, per project.

This means NB is on one side of the spectrum (fully automatic) where
Eclipse is at the opposite side (fully manual), while Intellij sits
somewhere in between.

Example instructions for all IDEs can be found at
http://griffon-framework.org/tutorials/1_getting_started.html#_tutorial_1_4
------------
QUOTE_END

I have not used apt-processors myself in Eclipse but this setup sounds
relatively complex compared to the other alternatives.

Are there plans to improve this? Without knowing the technical details
here, maybe a "Search in project classpath" option could be added?

If I understood him correctly, several customers are selecting NB or
IntelliJ because of that complex Eclipse setup and I promised him to
to ping the JDT developers about this.

Best regards, Lars
--
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com
[attachment "annotation_processing.png" deleted by Daniel Megert/Zurich/IBM] _______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev

_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev