Hi Jorg, Yes, I think rather just checking latest released source we should check the HEAD of components to ensure we will not break next planned release with java 9, at least we can fix if there is some issue from java9 RC it self, that will ensure future stability.
Looking at commons-text latest build via Travis its still using EA, Java HotSpot(TM) 64-Bit Server VM (build 9+175, mixed mode)., RC is build 9+181. I have raised requested Travis-ci to update it [1] , lets see. [1] https://github.com/travis-ci/travis-ci/issues/8233 Regards, Amey On Wed, Aug 9, 2017 at 1:33 PM, Jörg Schaible < joerg.schai...@bpm-inspire.com> wrote: > Hi Amey, > > Amey Jadiye wrote: > > > Hmm, isn't that easy with just Travis ? We just have to add java9 > > option(not sure it have RC) and trigger build it will automatically check > > build and tests. IIRC for few components we are having java9 Travis env > > already set. > > That would only ensure that the head revision runs with the Java 9 version, > that is supplied by Travis ... is that already the RC? > > Cheers, > Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
