On Thu, Mar 8, 2018 at 10:21 AM, ajs6f <aj...@apache.org> wrote: > > > On Mar 8, 2018, at 12:09 PM, Gary Gregory <garydgreg...@gmail.com> > wrote: > > > > That's all quite nice but the hard reality is that the tool chains out > > there are simply not ready for JPMS, as I've painfully learned > contributing > > to Log4j 2. MR Jars, module-infos, all of that breaks Maven plugins and > > tools left and right. So I do not see MR-jars as a viable options for any > > Commons Components at this time. The best we can do ATM is play with > > automatic module names in manifest files and look at what jdeps say > about a > > given component and see if we want to only depend on java.base or create > > Maven modules to compartmentalize dependencies. > > > > Gary > > > > "breaks Maven plugins and tools left and right" > > Yes. That's the point. That's perfectly fine. Kamila will find out which > break, and how, and what options we have to deal with them, and when we > might need to go upstream and come back, and she will document that, and > she will do what work can be done now on those problems. > > If Commons RDF does not release MR JARs as part of the GSoC project, but > we do understand specifically and in detail why and what the blockers are, > the project will have been a success. With respect, I think you are now > objecting to a project that hasn't actually been proposed, for which > success would be releasing MR JARs. _That is not what is being proposed._ >
Good! :-) Gary > > ajs6f > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
