Sorry, I asked the wrong question (similar to the above but different).
What I was trying to say is that if you stick jmh on the module path, the
annotation processor stops working:
https://stackoverflow.com/q/53927874/14731
If I explicitly add the JAR file to the annotation processor path then i
On 1/30/2019 9:40 AM, cowwoc wrote:
Seeing as `--add-modules=java.xml.bind` no longer works in Java 11 what is
the updated recommendation?
The Java SE Platform no longer includes JAXB. JEP 320 discusses where to
find standalone versions of JAXB (http://openjdk.java.net/jeps/320).
StackOverfl
Alan Bateman wrote
> On 22/11/2016 10:33, Eirik Bjørsnøs wrote:
>
>> :
>>
>> So again, I added -J-add-modules=java.xml.bind, and now my annotation
>> processor is loading.
>>
>> Given that my annotation processor does require java.xml.bind and I'm
>> using
>> --processor-module-path, my expectatio
On 22/11/2016 10:33, Eirik Bjørsnøs wrote:
:
So again, I added -J-add-modules=java.xml.bind, and now my annotation
processor is loading.
Given that my annotation processor does require java.xml.bind and I'm using
--processor-module-path, my expectation would be that javac would resolve
that re
Found it!
With --processor-module-path, JavacProcessingEnvironment.java:257 throws an
exception when
calling fileManager.getServiceLoader(ANNOTATION_PROCESSOR_MODULE_PATH,
Processor.class)
There's a catch for this exception at JavaCompiler, line 982:
catch (Abort ex) {
if (devVerbose)
> Currently, AFAIK, the processors on module path need to be registered in
> the ServiceLoader. For --processor-module-path, "-processor" can be used to
> select processors out of those registered in the ServiceLoader. If
> --processor-module-path is used and there is no "-processor", all
> process
On 21.11.2016 11:03, Alan Bateman wrote:
On 21/11/2016 09:46, Eirik Bjørsnøs wrote:
Alan,
| $ javac --help
| -processor [,,...]
|Names of the annotation processors to run; bypasses default
discovery process
Why does the "default discovery process" work with --classpath, but not
with
On 21/11/2016 09:46, Eirik Bjørsnøs wrote:
Alan,
| $ javac --help
| -processor [,,...]
|Names of the annotation processors to run; bypasses default
discovery process
Why does the "default discovery process" work with --classpath, but not
with --processor-module-path?
Is it simply an
Alan,
| $ javac --help
| -processor [,,...]
|Names of the annotation processors to run; bypasses default
discovery process
Why does the "default discovery process" work with --classpath, but not
with --processor-module-path?
Is it simply an omission, or is this by design?
With the curr
On 21/11/2016 00:22, Eirik Bjørsnøs wrote:
:
$ javac --processor-module-path
~/.m2/repository/com/example/annotation-processor/1.0-SNAPSHOT/annotation-processor-1.0-SNAPSHOT.jar
-sourcepath src/main/java src/main/java/module-info.java
src/main/java/com/example/module/SomeClass.java -g -nowarn -
Assuming Java 9 annotaton processors might need to provide
javax.annotation.processing.Processor as a service, I added:
provides javax.annotation.processing.Processor with
com.example.processor.ProcessorUsingJavaXmlBind
to module-info.java.
But still, no dice.
Eirik.
On Mon, Nov 21, 2016 at 1:
11 matches
Mail list logo
