OK, let's make the cheapest PR we can do now and see how it looks (no "Ant(ic)" please ;-) ). Then we can have an issue (or continue on this thread) about how to redo the wizards for multiple build systems. Indeed, if we go for the perfect solution we will still be stuck with having Ant the default for a long time...
--emi On Mon, Nov 26, 2018 at 10:26 AM <toni.ep...@eppleton.de> wrote: > I'm not rushing. I read the proposal by Jaroslav and he has a point. > Having ANT as the default is wrong. Maven should be the default. > So I created a PR which does exactly that (and nothing else). I provided a > (good) fix for the problem. > > I think it's great that this spawned a discussion about if we should unify > the project wizard and change the grouping completely. But my fear is, that > it prevents us from solving the initial problem. Some of the ideas are good > (like thinking about grouping project wizards in a more logical way), some > of them are bad in my opinion (like adding an extra step). All of them > require a lot more discussion. > > One example: > > There's a wizard for JavaFX with ANT and one with Maven. If we add a build > system choice in the wizard, the user will rightfully expect that this only > influences what build system is used. But actually it will do much more. > Both wizards create different applications, one is using FXML and CSS > (Maven), the other isn't (Ant). So we'll have to discuss what to do: For us > it's easier to convert the ANT project, but the Maven archetype is very > opinionated in promoting FXML and requires me to delete a bunch of files > every time I use it. So I would suggest to create a new archetype instead. > And now I'm lying under the car covered in oil, while I actually wanted to > change a lightbulb in the kitchen [1] > > The PR is the exact solution for the initial simple problem. I suggest to > treat the other changes as a different RFE. If we decide to unify the > wizards for different build systems, this is great, and it will wipe out my > changes before any user has seen them. If we don't find the time, or cannot > find a solution, then at least we've fixed the initial problem. > > --Toni > > [1] https://www.youtube.com/watch?v=AbSehcT19u0 > > > > -----Ursprüngliche Nachricht----- > Von: Emilian Bold <emilian.b...@gmail.com> > Gesendet: Sonntag, 25. November 2018 18:53 > An: NetBeans Dev@ <dev@netbeans.incubator.apache.org> > Betreff: Re: NetBeans - the UI for Maven > > I don't think there's any kind of rush to have a PR today. > > I like Geertjan's idea best: > > > IMHO there should be a single wizard named "Java SE Application" and a > > single wizard named "Java Web Applicaton", both of which, in step two > > or three, should let the user choose whether they want to build their > > Java application with Maven, Gradle, or Ant. > > If it's more work it's more work, but then users get to pick the build > system from a combobox and we just set the default to be Maven. > > I don't know that area that much but perhaps a we could have some SPI for > build systems and installing Gradle stuff will automatically add it to that > wizard combobox. > > Maybe users could also have an option to set their preferred build system > so it always picks Gradle (or Ant or Maven) next time. > > --emi > > > On Sun, Nov 25, 2018 at 7:48 PM <toni.ep...@eppleton.de> wrote: > > > Yeah, I realized it and uploaded them to the PR 😊. > > > > If we have something like: > > > > Java Application: > > - Maven based > > - ANT based > > Java Web 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. > > > > In my opinion, the best solution would be a selection box in the > > wizards, with the default set to Maven and ANT as the second option > where possible. > > But this would require a lot more effort. That's why for now I > > proposed this simple PR which also does the job to change the default > > Java build tool in project wizards from ANT to Maven. > > > > > > > > -----Ursprüngliche Nachricht----- > > Von: Neil C Smith <neilcsm...@apache.org> > > Gesendet: Sonntag, 25. November 2018 15:47 > > An: dev@netbeans.incubator.apache.org > > Betreff: Re: NetBeans - the UI for Maven > > > > On Sun, 25 Nov 2018, 14:14 Anton Epple <toni.ep...@eppleton.de wrote: > > > > > Putting all ANT related stuff in its own category has the benefit of > > > moving it out of focus, while still keeping it around for those who > > > need it. > > > > > > > A sub-category could do that too? Been doing that myself recently. > > Don't disagree with your point or approach either, just that it's > > possible to get some way towards what Geertjan and Chris are > > suggesting without code changes if that's the direction of travel. > > > > Attachments get stripped btw. > > > > Best wishes, > > > > Neil > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > > For additional commands, e-mail: > > dev-h...@netbeans.incubator.apache.org > > > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
