If you feel like fixing all the build warnings due to code not having generics and the like, sure! :-)
This is one of those "if it ain't broke, don't fix it" things. There is nothing wrong with source level 1.6 for infrequently modified code that's stable. If it were undergoing a major rewrite, I would expect the author to do that sort of thing. But doing it for the sake of aesthetics? Far better to spend time on actual features and bug fixes than cosmetic changes that don't affect semantics. It would be an utter waste of time, with the real risk that accidental semantic changes will be introduced that do break things. Don't do it unless the reward is worth the risk and the time that could be spent doing real work. -Tim On Mon, Jul 15, 2019 at 5:44 PM Brad Walker <bwal...@musings.com> wrote: > We have 417 project.properties files in the git repo.. > > These seem to be part of a Netbeans project for the various different > components. > > I've noticed the project.properties file contains the following: > > javac.source=1.6 > > Should we not think about maybe bumping that to 1.8? > > -brad w. > -- http://timboudreau.com
