On 05/04/2016 02:46 PM, Alan Bateman wrote:
On 04/05/2016 19:33, David M. Lloyd wrote:
Tools like Maven and JUnit are yet still having a difficult time
coping with the oddball module-info.java file.
Has been discussion on the JUnit tests about this? Aside from a few
usability issues then I haven't seen any issues with JUnit, it seems to
work just fine on class path or the module path as an automatic module.
Integration with Maven is the real problem in this case, I guess.
So far none of our software actually functions with Jigsaw, and the
prospect is not improving.
Can you expand a bit on this? Is this code that runs on JDK 8 but
doesn't run on JDK 9? Or maybe you mean that you or someone is migrating
some libraries or a complete stack to modules?
Mainly I'm referring to the unresolved issues at
http://openjdk.java.net/projects/jigsaw/spec/issues/. As yet I see no
evidence of activity from Mark nor anyone in the Jigsaw development on
any of these issues - no discussion, no response to discussion, nothing.
Not even rejection, just radio silence.
To be specific we need resolution to at least #ModuleNameCharacters,
#CyclicDependences, #LazyConfigurationAndInstantiation,
#MutableConfigurations, #ClassFilesAsResources, #VersionSyntax, and
#NonHierarchicalLayers for sure, in order for our system to interoperate
with Jigsaw (as opposed to trying to pretend it doesn't exist and won't
come back and bite us for Java EE 9). I think I can squeak out some
simple changes that disable version and module name syntax validation
for the simpler two, maybe even moving the existing rules in to the
system layer, but the rest require some real design thinking and
discussion, and I don't think I will have access to the resources needed
to contribute fixes to these without help from the Jigsaw team.
With the various SE 9 deadlines looming large, how realistic is it to
expect that even some of these issues will ultimately be resolved?
--
- DML
