*> there are three invocations of javac*
For me I'd describe it as only 2 invocations of javac.
That is, what above has as "second compilation" and "third compilation" is
I'd say is just 1 invocation of javac of the "example" module that includes
an annotation processor.
I'd describe it as 1
On 02/11/2020 00:02, Rob Bygrave wrote:
*> Since the type javax.annotation.processing.Generated has source *
* retention only, there are no @javax.annotation.processing.Generated
annotations in any class files compiled from source code emitted by your
processor*
The annotation processor
-
> From: Alex Buckley
> To: jigsaw-dev@openjdk.java.net
> Cc:
> Bcc:
> Date: Fri, 30 Oct 2020 08:34:55 -0700
> Subject: Re: @Generated requires java.compiler / what should my annotation
> processor do
> The type javax.annotation.processing.Generated was the replacement
&g
The type javax.annotation.processing.Generated was the replacement
introduced in Java SE 9 for the type javax.annotation.Generated.
Why was a replacement needed for the type javax.annotation.Generated?
Because the package javax.annotation belonged to Java EE, and was
removed in Java SE 11.
Are Java 9+ annotation processors using module path supposed to generate
source code that has a javax.annotation.processing.Generated annotation?
(which is part of java.compile)
I have an annotation processor that supports modules and is fine except
that when module applications use it the
