none of our software actually functions

[Alan Bateman]

On 04/05/2016 21:15, David M. Lloyd wrote:
>
> Integration with Maven is the real problem in this case, I guess.

Hervé Boutemy and Arnaud Hértier gave an update at Devoxx FR a few weeks 
ago:
https://speakerdeck.com/aheritier/fr-apache-maven-java-9-et-le-projet-jigsaw-at-devoxx-france-2016

There's a reference to a wiki page too:
   https://cwiki.apache.org/confluence/display/MAVEN/Java+9+-+Jigsaw

As we've always said, retrofitting modules to the Java Language and 
platform is a huge undertaking and requires the tools and eco system to 
work with us to make this happen. Members of the Maven community have 
been engaged with JDK 9 for a long tie and we'll do what we can here to 
help with the effort to upgrade Maven and its plugins to support the 
development and testing of modules.


> :
>
> 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.
I'm sure Mark will bring proposals or closure (with justification) to 
these issues in due course.


>
> With the various SE 9 deadlines looming large, how realistic is it to 
> expect that even some of these issues will ultimately be resolved?
The date that is approaching is the JDK 9 Feature Complete (FC) date. We 
have "the feature" in JDK 9 since jdk-9+111 with a refresh in jdk9/dev 
for jdk-9+118. There will be further iteration, tinkering and updates. 
Some parts of the implementation have replacement/improvements coming, 
the API needs improvements in a few areas, and I'm sure there will be 
changes to support some of the issues on the JSR list.

In past releases then features with a JSR continued to iterate a bit 
after FC, I expect the same here. Furthermore, with there will be 
feedback and usages with other features that will require re-work or 
changes after FC, that is normal and healthy.

The next milestone is ramp down starting Sep 1. I expect we will be in 
significant better shape by then.

-Alan