There is an error saying Jenkins doesn’t support Java 7 any for running Maven and that toolchains has to be used to compile and test using Java 7.
The fix for this is to configure the Jenkins job to use Java 8 by default and to use the Java 7 toolchain when a system property is set. I’ve done that and am re-running the build. Ralph > On Jul 16, 2017, at 11:29 AM, Matt Sicker <[email protected]> wrote: > > I didn't on that computer yet as I had just installed Java 9 for the first > time on it this morning. > > On 16 July 2017 at 13:10, Ralph Goers <[email protected]> wrote: > >> If you set the default JAVA_HOME how did the java 9 install override it? >> >> Ralph >> >>> On Jul 16, 2017, at 9:28 AM, Matt Sicker <[email protected]> wrote: >>> >>> Normally I set my default JAVA_HOME to 1.8 since 1.9 hasn't been >> compatible >>> with everything. Otherwise, I'll manually override JAVA_HOME on projects >>> that require an earlier version. >>> >>> On 16 July 2017 at 11:25, Ralph Goers <[email protected]> >> wrote: >>> >>>> How are you configuring your environment? I set my path and JAVA_HOME in >>>> /etc/profile. The Java installs never mess with that so the only >> “default” >>>> Java I have ever seen is the one I have configured. >>>> >>>> Ralph >>>> >>>>> On Jul 16, 2017, at 9:20 AM, Matt Sicker <[email protected]> wrote: >>>>> >>>>> Now that I'm trying this new build style out for the first time, I've >> got >>>>> some notes: >>>>> >>>>> 1. After installing Java 9, it's set to be the default JAVA_HOME if you >>>>> don't have one set. Maven has some JAXB-related missing module errors >>>>> currently (could be a plugin, could be Maven itself), so make sure to >> set >>>>> JAVA_HOME to 8 or 7 when running Maven. >>>>> 2. There's a similar problem when compiling log4j-scala (the separate >>>>> repo), but those issues appear to be more related to Scala itself. I >>>>> haven't really experimented with Java 9 and Scala yet as it won't be >> for >>>>> another couple years at least before Java 9 is ever required as the >>>>> baseline version for Scala (2.14 at the earliest if they keep this >>>> release >>>>> pattern up). I wonder if that's simply configuration related (e.g., the >>>>> toolchains config) or build plugins. Again, this is solvable by just >>>>> setting JAVA_HOME to Java 8 (required in that repo). >>>>> 3. Everything seems to work now on macOS. >>>>> >>>>> On 16 July 2017 at 07:14, Pierrick HYMBERT <[email protected] >>> >>>>> wrote: >>>>> >>>>>> Hello Ralph, noted and thanks, apologies I have no mac to test with. >>>>>> >>>>>> Le sam. 15 juil. 2017 à 05:51, Ralph Goers < >> [email protected]> >>>> a >>>>>> écrit : >>>>>> >>>>>>> OK - I have verified that FileAppenderPermissionsTest is flawed on OS >>>> X. >>>>>>> It is reading /etc/groups to find a group for the user. If it doesn’t >>>>>> find >>>>>>> a group then it tries to use the user’s name - which doesn’t work >>>> because >>>>>>> there is no group with that name. On MacOS /etc/groups is only used >> in >>>>>>> single user mode. It uses a directory in “normal” mode, so this >> method >>>> of >>>>>>> finding a user’s group is just not going to work. I set the group to >>>>>>> “staff” on OS X as that will typically work unless the user has done >>>>>>> something custom. >>>>>>> >>>>>>> Ralph >>>>>>> >>>>>>>> On Jul 14, 2017, at 8:32 AM, Apache <[email protected]> >>>>>> wrote: >>>>>>>> >>>>>>>> Yes. I did that to the rolling tests but I don't know whether the >>>> tests >>>>>>> are bad for the permission stuff or whether the functionality doesn't >>>>>> work >>>>>>> on MacOS, in which case it would need to be disabled. >>>>>>>> >>>>>>>> Ralph >>>>>>>> >>>>>>>>> On Jul 14, 2017, at 8:01 AM, Gary Gregory <[email protected]> >>>>>>> wrote: >>>>>>>>> >>>>>>>>> I assume you will be adding JUnit Assume calls to skip these tests? >>>>>>>>> >>>>>>>>> Gary >>>>>>>>> >>>>>>>>>> On Jul 14, 2017 00:01, "Ralph Goers" <[email protected]> >>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> After ignoring the test causing the previous problem I am now >>>>>>> encountering >>>>>>>>>> errors with the new permissions test. I am disabling the >>>>>>>>>> RollingAppenderDirect test since it also will have the same >> problem >>>>>>> with >>>>>>>>>> FileWatcher, but I don’t know the cause of the other failures. >>>>>>>>>> >>>>>>>>>> Ralph >>>>>>>>>> >>>>>>>>>> ERROR] Failures: >>>>>>>>>> [ERROR] FileAppenderPermissionsTest.testFileUserGroupAPI:181 >>>>>>>>>> expected:<rw-[----]--> but was:<rw-[r--r]--> >>>>>>>>>> [ERROR] FileAppenderPermissionsTest.testFileUserGroupAPI:183 >>>>>>>>>> expected:<[rgoers]> but was:<[staff]> >>>>>>>>>> [ERROR] FileAppenderPermissionsTest.testFileUserGroupAPI:181 >>>>>>>>>> expected:<rw-r[w--]--> but was:<rw-r[--r]--> >>>>>>>>>> [ERROR] FileAppenderPermissionsTest.testFileUserGroupAPI:181 >>>>>>>>>> expected:<rw[xrwxrwx]> but was:<rw[-r--r--]> >>>>>>>>>> [ERROR] >>>>>>> RollingAppenderDirectWriteTempCompressedFilePatternTest. >>>> testAppender:94 >>>>>>>>>> No temporary file created during compression >>>>>>>>>> [ERROR] Errors: >>>>>>>>>> [ERROR] JeroMqAppenderTest.testClientServer:70 » TestTimedOut >>>> test >>>>>>>>>> timed out after 600... >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>> >>>>>> Best Regards / Cordialement / С уважением, >>>>>> >>>>>> Pierrick *HYMBERT* / Пьеррик *ИМБЕР* >>>>>> >>>>>> *+Pierrick <https://plus.google.com/u/0/105713262389092625238> / >> Skype >>>> / >>>>>> LinkedIn <https://linkedin.com/pub/pierrick-hymbert/51/506/357>* >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Matt Sicker <[email protected]> >>>> >>>> >>>> >>> >>> >>> -- >>> Matt Sicker <[email protected]> >> >> >> > > > -- > Matt Sicker <[email protected]>
