On Fri, 2019-09-20 at 12:08 +0200, Radu Cotescu wrote: > +1 and the sooner the better, since it reduces potential migration > efforts. > > > On 20 Sep 2019, at 11:31, Robert Munteanu <[email protected]> > > wrote: > > > > I would encourage everyone when making a change to a module or when > > releasing to update to the latest parent pom. It usually is not too > > much work and keeps us using the latest improvements. > > > > On top of this I would also argue that it would make sense to start > testing our builds with the latest Java releases, so that when the > next LTS is released we’re ready to support it without too much > effort.
What do you mean by 'builds'? All modules? Note that building all modules with Java 11 would require updating to a more recent parent pom. For the moment we run the Sling ITs with Java 8, 11, and 13. See [1] and [2]. Thanks, Robert [1]: https://builds.apache.org/job/Sling/job/sling-org-apache-sling-launchpad-testing/job/master [2]: https://cwiki.apache.org/confluence/display/SLING/Java+version+support
