Hi JB, Sorry I introduced the easy mock SNAPSHOT. Per the discussion here[1], easymock 3.7 release which can work with JDK11 should not be far.
Anyway, we can downgrade to easymock 3.6 so far while waiting for easymock 3.7 release. Though this will cause VerifyMojoTest failed with JDK11, I will add a profile to disable this test with JDK11 until we have easymock 3.7 available. Btw, could we also have CI build for master using JDK10 and JDK11; therefore we can catch any test failure in the first time. [1]https://github.com/easymock/easymock/issues/218 <https://github.com/easymock/easymock/issues/218> Cheers －－－－－－－－－－－－－ Freeman(Yue) Fang Red Hat, Inc. FuseSource is now part of Red Hat > On Jul 5, 2018, at 4:50 PM, Jean-Baptiste Onofré <[email protected]> wrote: > > Hi guys, > > just a little reminder: when possible, please avoid to use SNAPSHOT in > dependency (or only on PR, not merged on master). > > SNAPSHOT dependencies breaks the build and so Karaf SNAPSHOTs are not > deployed anymore. > It also block release as we can't release project containing SNAPSHOT > dependencies. > > For instance, we did a commit on master this morning upgrading to > Easymock 3.7-SNAPSHOT (to be able to build with Java 10/11), and Jenkins > is broken (also local build). > > I will fix that, but, please, keep in mind to avoid SNAPSHOT > dependencies when possible. > > Thanks ! > Regards > JB > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com
