IMHO, setting the source & target to 1.8 (or whatever the lower end of your support range is) and running a CI job with a range of versions is the way to go (1.8, 11, etc) That way this uncovers the issues similar to you have mentioned and retains backward compatibility with any of the dependencies you update. I do something similar at my day job, and IIRC Spring does this too.
On Mon, Jun 17, 2019 at 10:37 AM Shawn McKinney <[email protected]> wrote: > Hello, > > An assertion about Java9 support… > > Directory projects should support Java9++ but not require it. > > The adding part is pretty easy. Update the pom, change the compiler > plugin, add missing dependencies for JAXB, … > > The not requiring is perhaps the tricky part. > > What is the best way to allow the user to pick which compiler to use > without boxing them into one or the other? > > Open to suggestions, comments, laments, etc... > > Thanks, > —Shawn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
