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 178258 - [68cat] Optional property in new Maven project is required
Summary: [68cat] Optional property in new Maven project is required
Status: RESOLVED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 6.x
Hardware: PC All
: P3 normal with 2 votes (vote)
Assignee: Jesse Glick
URL:
Keywords:
: 189996 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-12-07 10:03 UTC by jpleed3
Modified: 2010-11-20 06:11 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Screenshot of new Maven project wizard (52.71 KB, image/x-png)
2009-12-07 10:03 UTC, jpleed3
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jpleed3 2009-12-07 10:03:47 UTC
Created attachment 92235 [details]
Screenshot of new Maven project wizard

The package property in a new Maven project has optional beside it, but the project cannot be created without it. See attached screenshot.
Comment 1 Milos Kleint 2009-12-08 05:21:55 UTC
it's not optional within the wizard, as we do additional checks on package name correctness. The last time I tried you could create a project with invalid package names.
Comment 2 jpleed3 2009-12-08 07:30:37 UTC
Optional - adjective, not required or mandatory.

I am of the opinion that an optional label for a required field is confusing for the user. I'm simply suggesting either of the following:

1. If a user enters no package name, then don't create any. When I transitioned to Maven from NB Ant projects, I was copying packages from one project to the other so I wasn't going to use the created packages anyway.

or

2. Remove the optional label.
Comment 3 Milos Kleint 2009-12-08 08:15:25 UTC
if it boils down to removing optional hint, then I'm all for it. I didn't notice it in the picture. We populate it with sensible defaults therefore it should not be a problem.

re 1: having new maven projects created just for the sake of migration of ant projects is not a supported usecase in this UI. If we decide to write a migration tool, it will no use the archetypes plugin.
Comment 4 mvfranz 2010-02-02 08:53:59 UTC
Will the text '(Optional)' be removed from the wizard?  I find it very confusing and actually incorrect as it is not optional.
Comment 5 Antonin Nebuzelsky 2010-07-30 15:17:51 UTC
Reassigning to default owner.
Comment 6 ftg314159 2010-08-26 12:22:41 UTC
Please leave it optional and make it so.  In designing a hierarchy of POMs that inherit plugins and dependencies going down the line, it is very common to want a maven project with no source, in which case you just have to go in and delete stuff afterwards.
Comment 7 Jesse Glick 2010-11-16 22:44:02 UTC
*** Bug 189996 has been marked as a duplicate of this bug. ***
Comment 8 Jesse Glick 2010-11-18 20:18:56 UTC
(In reply to comment #6)
> it is very common to want
> a maven project with no source, in which case you just have to go in and delete
> stuff afterwards.

Then you want to use a different archetype, unlike Quickstart which always creates source files; that is not an issue of the IDE's wizard.
Comment 9 Jesse Glick 2010-11-18 20:26:46 UTC
core-main #9c640d6c63a2
Comment 10 Quality Engineering 2010-11-20 06:11:59 UTC
Integrated into 'main-golden', will be available in build *201011200001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/9c640d6c63a2
User: Jesse Glick <jglick@netbeans.org>
Log: #178258: [68cat] Optional property in new Maven project is required