Michael Bien

well i would like to have all new-project wizards use the same new-java-mainclass template. Just like the old ant project did/does. It makes sense for the user too. One file...

> > well i would like to have all new-project wizards use the same new-java-mainclass template. Just like the old ant project did/does. > > +1 to that. Is that...

> org.netbeans.modules.java.source.builder issue it that javadoc cannot find the com.sun.source.tree.CaseTree.CaseKind; > I compile on jdk 11 and this is introduced in jdk 12 or maybe with the nb-javac. what if...

> @mbien this could be done in a CI build but how to do that at the time you edit the module within IDE for example. I don't think this...

> @mbien building too ahead make some module not compilable (source target too low 1.6 for openide.io as an example) i think we could rise everything to 8 if necessary....

> I will later sqash all of that in one commit so we could resync. on true master branch :D I've miss the -meta.branch=master I can build until the end...

this is going to be difficult to review :/ would it be possible to split "interesting" changes like the build logic for `javadoc.nbjavac=true` into separate commits?

added NB14 milestone to keep this on the radar.

@timboudreau github has a "hide whitespace changes" setting which helps a bit (little cog on the review tab). In any case, this PR needs rebasing to get a fresh CI...

before I forget: the commits need to have a real name and valid address in the header.