This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 139532 - create "empty" project without archetype
Summary: create "empty" project without archetype
Status: RESOLVED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
: 166869 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-07-10 08:43 UTC by kawazu428
Modified: 2010-08-05 13:39 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kawazu428 2008-07-10 08:43:57 UTC
So far, creating a maven2 project there's either the choice of using an archetype or creating a project based upon an
empty pom. Currently I would see it desirable to be capable of creating an "empty" maven project consisting just of

- a project folder and
- a pom.xml containing the minimum subset of information required for that (groupId, artifactId, version).

So far, using any archetype usually ends up in throwing away quite a bit of things not always required (default
packages, testing libs, ...).
Comment 1 Milos Kleint 2008-07-10 13:12:01 UTC
not sure it's actually necessary to include, additional UI clutter needs to be evaluated. how to explain the basic
difference? is it s usable setup for les experienced devs?
Comment 2 kawazu428 2008-07-10 13:17:20 UTC
Usable setup for less experienced developers? Probably not, I assume. More of a "convenience" feature to all those who
know pretty well what they want to do. In my opinion it fills the "gap" between being either pushed through a
quickstart-based empty project or being in need of using external tools (shell, explorer, that kind of stuff) to create
an empty folder+pom.xml simply to create a Maven2 project "from existing pom.xml". Overally I don't think it's that
difficult a feature that would eradicate one more situation in which one once in a while is forced to use external tools
(and/or abuse the "Favorites" view...). ;)
Comment 3 Milos Kleint 2009-06-11 08:11:19 UTC
*** Issue 166869 has been marked as a duplicate of this issue. ***
Comment 4 Jesse Glick 2009-06-11 21:55:54 UTC
Needed for creating a tree of modules from inside the IDE. (Could create pom.xml manually but you would have to find
another POM project to copy xmlns & required fields from, unless you have memorized all this.)
Comment 5 Antonin Nebuzelsky 2010-07-30 15:16:57 UTC
Reassigning to default owner.
Comment 6 Jesse Glick 2010-08-04 13:55:06 UTC
core-main #679ba45f7626
Comment 7 Quality Engineering 2010-08-05 03:20:16 UTC
Integrated into 'main-golden', will be available in build *201008050001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/679ba45f7626
User: Jesse Glick <jglick@netbeans.org>
Log: #139532: add standard archetype for POM project.
Could in the future use a special wizard to make this nicer:
- show at top level rather than as an "archetype"
- do not show "package" field since it is unused
- eliminate " Maven Multi Project" suffix in <name> which is irritating
- set default New Project location so can easily add submodules