On Fri, Mar 23, 2018 at 5:19 AM, Martijn Verburg <martijnverb...@gmail.com> wrote: > Hi All, > > Stephen's comments are in his blog post: http://blog.joda.org/2018/03/j > pms-negative-benefits.html > > He does raise some interesting points. Perhaps it's worth spending some > time before 11 is out to see if there is a combination of Maven and JPMS > changes / clarifications that can address some of these pain points. > > If Stephen is missing something, then that's an area we could document > (and/or publicise better if already documented. That is something I and > others can help to address through the usual JUG Leaders / Champions / Info > Q etc channels. > > @Stephen are you able to share the source code? It may be that there is > another > path that could be explored to mitigate some of the challenges you faced. > > @Robert - I've been thinking about the difficulty of getting enough > engineering time for Maven committers to add support for major features > like JPMS. I'll start a separate thread with you on that.
Case in point: I've had https://github.com/apache/maven-compiler-plugin/pull/1 sitting out there since January. This commit is a key to what is at least a somewhat workable strategy for MR JARs and multi-JVM build and testing for us. Robert has said that the change is acceptable, but indicated that there may be a resource problem in terms of getting the plugin to a releasable state. I (and others I work with) are more than willing to contribute what extra time we have to fixing or improving things in Maven and its plugins, and even in the JDK itself, but the other side of that is that the fixes do need to be accepted in a timely manner. With Java 11 just around the corner, the time is now. -- - DML
