Bug 224999 - [73cat] offer project type in one unified method
[73cat] offer project type in one unified method
Status: NEW
Product: projects
Classification: Unclassified
Component: Generic Projects UI
7.3
PC Windows 7
: P3 with 7 votes (vote)
: TBD
Assigned To: Milos Kleint
issues@projects
: UI_REVIEW
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-16 21:51 UTC by muellermi
Modified: 2013-01-17 14:32 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments
IDE log (49.26 KB, text/plain)
2013-01-16 21:52 UTC, muellermi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description muellermi 2013-01-16 21:51:27 UTC
Product Version = NetBeans IDE 7.3 RC1 (Build 201301102100)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.7.0_11
Runtime = Java HotSpot(TM) 64-Bit Server VM 23.6-b04

When I want to add a new project, I first choose choose a category, e.g.
Java Web and the the concrete project, e.g Web Application. Then the 
project skeleton is created by NetBeans, allways using Ant.

If I want to use Maven, I first have to select the build tool, Maven, and 
then the project type, e.g. Web Application.

My proposal is to offer the user one unified method to create new projects.
Category -> Project Type, then choose build tool Ant, Maven.

This might be enhanced in the future, e.g. Buildr, Graddle

Some special types like" Maven, create from archetype" might be placed in the "Other" category
Comment 1 muellermi 2013-01-16 21:52:14 UTC
Created attachment 130314 [details]
IDE log
Comment 2 Marian Mirilovic 2013-01-17 08:28:47 UTC
I think this is dup of already reported bug, but can't find number
Comment 3 Milos Kleint 2013-01-17 08:36:03 UTC
the current grouping historically started this way because maven project were limited in functionality in terms of what was supported in the IDE, which is somewhat still the case (no javafx, platform based development is not equal).
Comment 4 Milos Kleint 2013-01-17 14:32:57 UTC
additionally the requirement to choose between ant and maven is not easily decided by those users that have either no opinion or no knowledge about build systems. Moving the Maven templates into a separate category spared those users the need to decide. Ant projects mostly attempt to hide the build system behind the covers while maven not always does. The audience might be entirely different.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo