I would say a good step forward is to report errors people see with running Groovy on JDK 9 on JIRA right now. Because Groovy _does run_ on JDK 9. Only it does with lots of unfriendly warnings (and will stop working with JDK 10/18.3). If there are showstoppers, we're not aware of them.
2017-10-04 16:18 GMT+02:00 Andrew Bayer <[email protected]>: > No worries - I just wanted to get the ball rolling and get myself aware of > things so that I can calm Jenkins people down that no, we won't be stuck on > Java 8 forever. =) > > A. > > On Wed, Oct 4, 2017 at 4:17 PM, Paul King <[email protected]> wrote: > >> Hi Andrew, >> >> We have discussed a few things quite often but don't have a definitive >> list of remaining tasks. There are a mix of big and small tasks, so we >> should definitely try to carve off a list of tasks that aren't too hard for >> others to do. I won't get time to look at this until next week. >> >> Cheers, Paul. >> >> On Wed, Oct 4, 2017 at 10:26 PM, Andrew Bayer <[email protected]> >> wrote: >> >>> Hey all - >>> >>> So over in the Jenkins project, we're more than a little bit freaked out >>> about Groovy + Java 9, since Groovy is absolutely critical to Jenkins. I >>> think I can carve out time to work on the problems with Groovy + Java 9, >>> but to a certain extent, I'd be jumping into the jungle without a map. =) >>> Do we have any kind of roadmap for what needs to be done, or any specific >>> concrete tasks that need to be tackled? >>> >>> A. >>> >> >> >
