Re: New JDK 9 module chasing tool (was: Getting a list of "to be modularized" dependencies in topological order?)

2018-02-24 Thread Mark Raynsford
On 2018-02-24T09:47:02 +1000 Paul King wrote: > Looks good. > > A small bit of feedback. I tried using it on a project (Groovy) with > an "all" artifact that has no jar - just references other jars. Even > when I specified "pom" it tried to look for the jar > artifact. Despite the error stacktr

Re: New JDK 9 module chasing tool (was: Getting a list of "to be modularized" dependencies in topological order?)

2018-02-23 Thread Paul King
Looks good. A small bit of feedback. I tried using it on a project (Groovy) with an "all" artifact that has no jar - just references other jars. Even when I specified "pom" it tried to look for the jar artifact. Despite the error stacktrace it continued and still seemed to produce the correct res

New JDK 9 module chasing tool (was: Getting a list of "to be modularized" dependencies in topological order?)

2018-02-23 Thread Mark Raynsford
I've published a plugin here: https://github.com/io7m/modulechaser It produces a standalone XHTML report detailing the modularization status of the transitive dependencies of any project you point it at. The status table is presented in reverse-topological order; start bugging maintainers at the