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 14484 - Need an "uncategorised" element in the list of groups/categories, or need to force categorisation of new modules
Summary: Need an "uncategorised" element in the list of groups/categories, or need to ...
Status: RESOLVED INVALID
Alias: None
Product: obsolete
Classification: Unclassified
Component: collabnet (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P4 blocker (vote)
Assignee: support
URL: http://cpplite.netbeans.org/servlets/...
Keywords:
Depends on:
Blocks:
 
Reported: 2001-08-16 13:36 UTC by jcatchpoole
Modified: 2009-11-08 02:28 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jcatchpoole 2001-08-16 13:36:15 UTC
See the URL above, the admin page for the "das" category.  On this page is a 
list of modules in that category - there are 4 shown.

http://www.netbeans.org/servlets/DomainProjects confirms that there are 4
modules in the das category.

Go to for example http://archivesupport.netbeans.org/servlets/ProjectEdit , the
Admin page for the archivesupport module.  It is shown as being in the "das"
category.

I think this is just the default displayed category for a module that is
uncategorised, das just happens to be first in the alphabetical list of 
choices.

If archivesupport is actually uncategorised, it should be shown as such on
this page.  Alternatively, someone creating a new module should be "forced" 
to choose a category, so nothing is ever uncategorised.

archivesupport is just an example, there are many NB modules which appear to
be uncategorised, and show up as "das" - jpython, xmlbeans, xml, look, edu, ...
Comment 1 jcatchpoole 2001-10-30 14:22:20 UTC
AFAIK all the categories have been fixed, ie, manually assigned to
a category.  Perhaps this situation arose as a result of the modules 
being "imported" rather than created from scratch ?  Is assigning 
a category *required* when creating a new module ?  If a module
really is uncategorised, is it displayed as such ?
Comment 2 Taska 2001-10-30 16:29:12 UTC
Looking into this.
Comment 3 Taska 2001-11-02 20:41:44 UTC
Assigning a category is required when adding a new module.  In the
second step of adding a new module, you are required to choose from
the list of categories to add a new module.  'das' does happen to be
first in the list, and therefore if you don't change it, your module
will be put into the 'das' category.

The fact that these modules were placed unexpectedly into the 'das'
category was an artifact of migration.
Comment 4 Unknown 2004-11-18 12:33:11 UTC
closing...
Comment 5 Marian Mirilovic 2009-11-08 02:28:27 UTC
We recently moved out from Collabnet's infrastructure