Github user phang98 commented on the pull request:
https://github.com/apache/maven/pull/64#issuecomment-169261641
I apologize for not fulfill my earlier commitment. :(
Happy new year and get the new traction again on this topic.
Will spend some time this weekend if possible.
Op Tue, 05 Jan 2016 22:55:03 +0100 schreef Jochen Wiedmann
:
On Thu, Dec 31, 2015 at 1:01 PM, Robert Scholte
wrote:
The next blocking issue requires some work by the Apache Maven team
and/or
at the QDox project[2].
QDox is a Java Parser which is used to read javadoc and/or annotations
On Thu, Dec 31, 2015 at 1:01 PM, Robert Scholte wrote:
> The next blocking issue requires some work by the Apache Maven team and/or
> at the QDox project[2].
> QDox is a Java Parser which is used to read javadoc and/or annotations from
> source in order to generate xml or other Java files.
> With
Sure, no problem
Op Tue, 05 Jan 2016 22:20:16 +0100 schreef Paul Benedict
:
No problem, Robert. I just wanted to collaborate (since both you and I
are
on Maven and OpenJDK lists) and offer alternative options. Personally, my
interest is generating module-info.java from dependencies; so if
No problem, Robert. I just wanted to collaborate (since both you and I are
on Maven and OpenJDK lists) and offer alternative options. Personally, my
interest is generating module-info.java from dependencies; so if you ever
get to that problem space, please reach out to me so I can discuss some
idea
You could specify the "requires" by reading the module-info when available
in a jar or by converting the file name when not available.
However, "requires" could also be "requires public"[1]. That's all up to
the developer. All other sections must be handcrafted. For that reason I
mentioned th
However, you could theoretically generate module-info.java based on
dependencies, if you knew which dependencies were modules. Given that the
"what is a module" metadata is not being captured today, you would be
required to inspect the contents of the jars in your dependency graph and
then add that
Let me first make clear that I chose Maven as a reference application. I
wanted a real life multimodule example, not as big as SCM and with enough
classes. I wanted to test if I could package/compile this project if I
added module-info.java files to it and confirm that all the other plugins
