On 29.06.23 07:52, Paul King wrote:
[...]
I would be interested in looking at earlier attempts like V2 to see if
advances in the meantime now make them more feasible.
[...]
On Mon, Jun 26, 2023 at 10:16 PM Jochen Theodorou mailto:blackd...@gmx.org>> wrote:
[...]
V2:
Collect class
On 29.06.23 20:39, Christopher Smith wrote:
Implementing javax.annotation.processing would cover a lot of surface
area because it exposes the Java AST (via the RoundEnvironment methods)
and the entire TypeMirror "Spock in a goatee" representation of the Java
classes under processing. This means t
I also use Lombok almost universally for Java files, so I understand its
importance! I was paying attention to the stub-compilation approach, which
would still run through javac and thus native Java files would be affected.
If you're thinking more on the joint side, then I'd have to think more
befo
On 29.06.23 19:28, Christopher Smith wrote:
One note I'll add is that while Lombok was presented as an example of a
Java annotation processor, it really isn't—it's a monkey-patch of javac
itself, as otherwise annotation processors can't modify classes, just
add new ones.
I am actually aware of
One note I'll add is that while Lombok was presented as an example of a
Java annotation processor, it really isn't—it's a monkey-patch of javac
itself, as otherwise annotation processors can't modify classes, just add
new ones. Regarding "regular" annotation processors, it would be possible
to impl
On 29.06.23 16:24, Milles, Eric (TR Technology) via dev wrote:
Thanks for raising that issue. It has been a limitation for some folks for
quite a while. I am very keen to improve our joint compilation process if we
can.
I was actually wondering if someone really still cares.
I do get issue
>> Thanks for raising that issue. It has been a limitation for some folks for
>> quite a while. I am very keen to improve our joint compilation process if we
>> can.
>
> I was actually wondering if someone really still cares.
I do get issues quite often (for groovy-eclipse tooling) that expect
On 29.06.23 07:52, Paul King wrote:
Hi Jochen,
Thanks for raising that issue. It has been a limitation for some folks
for quite a while. I am very keen to improve our joint compilation
process if we can.
I was actually wondering if someone really still cares.
I did try one experiment to imp
Hi Jochen,
Thanks for raising that issue. It has been a limitation for some folks for
quite a while. I am very keen to improve our joint compilation process if
we can.
I did try one experiment to improve the V0 process by making transforms
smarter and idempotent. Essentially, I was trying to get
Hi all,
yesterday I was playing around with joint compilation and I want to
share some thoughts:
current state (afaik): V0
Groovy creates stubs, Javac compiles Java and stubs, Groov compiles
against generated classes. Annotationprocessing on Java should work, on
Groovy it depends on the phase.
10 matches
Mail list logo
