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 106000 - Search in the Plugins dialog does not work correctly
Summary: Search in the Plugins dialog does not work correctly
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Autoupdate (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks: 109131
  Show dependency tree
 
Reported: 2007-06-07 12:32 UTC by Petr Jiricka
Modified: 2007-08-08 13:27 UTC (History)
4 users (show)

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 Petr Jiricka 2007-06-07 12:32:33 UTC
Continuous build from June 7, 2007, Mac OS X.

1. Open the Plugins dialog, go to New Plugins tab
2. Type 'blueprints' in the Search field
=> nothing is found
3. Go to Settings tab, check 'Show details of all plugins'
4. Go back to New Plugins tab
=> now one module is found

The two cases should behave consistently, the display view should not make any
difference to the functionality
Comment 1 _ ludo 2007-06-15 19:47:36 UTC
P2: regression
people just cannot discover new plugins like EJS editor, or worse GlassFish V3.
V3 is a very important new runtime we want people to try and give early feedback.
This is a huge regression from previous UI where plugin are discoverable.
Now they are just not discoverable.

Please, fix this for M10 or I need to find other strageties to expose  these plugins..
Comment 2 Antonin Nebuzelsky 2007-06-20 13:34:03 UTC
The thing is that in the default view (the view on features aka plugins) a module may be hidden inside a bigger feature
(not the case with Glassfish v3 now, BTW).

The search filter works over a certain properties of the visible items, like the name or the description.

A way to fix this problem would be for example to list the descriptions of the individual modules within the description
of the big feature. This would make the description text of the feature much longer than it is now, but if the
description text is well structured, it could work for the users nicely. They would then be able to search for even the
smallest parts of a big feature using the Search filter and identify the big feature they need to install to get the
smaller part they are interested in.
Comment 3 rmatous 2007-06-20 13:55:17 UTC
After fixing #106799 is not so severe problem because descriptions in default view (features) contain also display names
of modules that form it, so you can search for them: P3 now, I think
Comment 4 rmatous 2007-06-20 13:55:36 UTC
P3
Comment 5 Jiri Rechtacek 2007-08-08 13:27:25 UTC
After integrating issue 110566 this problem was fixed. Modules itself can control its visible state in Plugin Manager
(attribute AutoUpdate-Show-In-Client: false or true in manifest.mf).