Re: Thoughts on MR-Jar support in Maven

not really IMHO the question here is to create one multi-release jar, not how to maintain many (one-)release jars from one sourcecode: MR jars are done to avoid the release- specific jar approach (that preprocessing makes viable) Regards, Hervé Le vendredi 24 mars 2017, 11:08:49 CET Aldrin

Re: Thoughts on MR-Jar support in Maven

Wouldn't preprocessing help? https://blog.jooq.org/2016/03/01/how-to-support-java-6-8-9-in-a-single-api/ -- -- Aldrin Leal, / http://about.me/aldrinleal On Fri, Mar 24, 2017 at 11:01 AM, Andreas Sewe < s...@st.informatik.tu-darmstadt.de> wrote: > Hi, > > > I would have

Re: Thoughts on MR-Jar support in Maven

Hi, > I would have thought that it was not Maven's responsibility to ascertain > that test passed in various JDKs, old and new. I agree that is is not Maven's responsibility to (out of the box) execute the tests against multiple JREs. If you think it is, one can just as well argue that it should

Re: Thoughts on MR-Jar support in Maven

On Fri, 24 Mar 2017 12:20:16 +0100, Ceki Gülcü wrote: I would have thought that it was not Maven's responsibility to ascertain that test passed in various JDKs, old and new. With the classic setup there's only one JDK and all tests are at least executed with that JDK, all

Re: Thoughts on MR-Jar support in Maven

Hi Robert, I would have thought that it was not Maven's responsibility to ascertain that test passed in various JDKs, old and new. Nevertheless, there is no doubt that once you pay attention to the details, things can get messy awfully quick. BTW, thank you for your previous response.

Re: Thoughts on MR-Jar support in Maven

Hi Ceki, the compilation-part isn't the real issue (it is acutally the easy part), but e.g. the testing-part is. You must ensure that surefire is also executed at least twice: once for pre-java9 and for java9. And what to do with other plugins which are part of the lifecycle up until the