+1 to making Maven the default. I agree that we should not force users to choose between Maven or Ant when creating a new project. Just make Maven the default and allow the user the ability to change to Ant, if desired.
Josh Juneau [email protected] http://jj-blogger.blogspot.com https://www.apress.com/index.php/author/author/view/id/1866 > On Nov 25, 2018, at 12:57 PM, Neil C Smith <[email protected]> wrote: > > Hi, > >> On Sun, 25 Nov 2018 at 17:48, <[email protected]> wrote: >> >> Java Application: >> - Maven based >> - ANT based >> >> This doesn't really move ANT out of sight, and is only slightly better >> than what we have now. It also adds one more click to the wizard. > > > That's not quite what I envisaged by using the hierarchy for this though - > thinking more about > > Java > - Java Application (Maven) > - POM Project > - Project with Existing POM > - Ant based > - Java Application (Ant) > - Java Free-Form Project > NetBeans > - NetBeans Application (Maven) > - NetBeans Module (Maven) > - Ant based > - NetBeans Application (Ant) > - NetBeans Module (Ant) > Java Web > - ... > > Something like that anyway. ie. only the non-default / legacy stuff is in a > sub-category. > > Agree with Emi that there's no rush for a PR on the basis that we're > talking NB11 earliest, but less sure how the wizard combobox option would > actually be preferable to revising project selection in practice. Depends > how much each type of project overlaps across build systems I guess? > > Best wishes, > > Neil
