Steady progress is being made, but some significant technical challenges remain. There is, more importantly, not enough time left for the broad evaluation, review, and feedback which such a profound change to the Platform demands. I therefore propose to defer Project Jigsaw to the next release, Java 9. In order to increase the predictability of all future Java SE releases, I further propose to aim explicitly for a regular two-year release cycle going forward.
For a while OpenJDK has had a prototype (download and evaluate here). Reinhold says that maintaining compatibility with existing code has been a "delicate task". They also have not started to plan how they will support various containers for IDEs, app servers, etc.
The comments on Reinhold's blog were split pretty evenly between supporters and 'the annoyed'.
From Guillaume Laforge (major Groovy contributor)
We didn't go too far with modularity in Groovy 2... because we didn't want to duplicate what was supposed to be coming in Java 8.
But now, it means it won't be in the hands of developers before 2 years, and in production before 3 years :-(
It means that Jigsaw, if it ever ships, will have been 5+ years in the making. That sounds a lot, even for such a big feature and task.
Johannes Brodwall however, was fully in agreement that Jigsaw should not be allowed to hold up Java 8:
DON'T HOLD THE TRAIN. The five years from Java 6 (which itself was disappointing) to Java 7 nearly killed the language.
But understandably, some were disappointed that Jigsaw, which was first proposed for Java 7, is probably not coming till Java 9 now. Markus Karg suggested they give up on the idea and just tell people to use Maven.
So... How does this news sit with you? Are you with the "Just use Maven" crowd? Do you think it's important that Java 8 not be delayed?