[jdt-core-dev] Questions about the usage of module with JDT 3.13.50

[Simon Urli <simon.urli@xxxxxxxx>]

Hello,

I'm using the JDT core library for an open-source projet which analyzes 
and transform java source code (for more information: 
https://github.com/INRIA/spoon/)

I'm trying to put in our library the concept of java modules introduced 
by JDK9. I saw that with the release of JDT 3.13.50, this concept is 
available in JDT through ModuleDeclaration.

But I have some issues when using JDT with modules.
So first of all: is there any documentation about the usage of JDT core 
which documents module, module declaration and anything related to those 
concepts? It could help me a lot for the future :)

Secondly: I saw that there is new arguments "-module-source-path" and 
"-module-path" in JDT. What are the differences between them? And are 
they useful when building a project with a unique module?

Apparently in https://bugs.eclipse.org/bugs/show_bug.cgi?id=487421#c2 
Jay Arthanareeswaran said that module-source-path should not be used for 
single module: should this comment be taken as a documentation?

For information, I tried to use JDT on a simple projet with one module 
and I have errors like "The package XXX does not exist or is empty".
I spotted that a bug 
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=525603) like this has 
been fixed recently, so I imagine my error will be fixed to the next 
release... which led me to the next question:

is there already a planned date for the next maven release of JDT?

Finally, in my library I'm trying to assign to each type the module it 
belongs to: is there a way to know from a TypeDeclaration or its 
CompilationUnit scope in which module the type is declared?

Thanks for your clarification,

Simon.