NB6PluginManagerIssues

NB6 Plugin Manager Issues

Problem: When IDE runs offline ('with fresh userdir') then all tabs incl. installed are empty because the cache was not initialized
Solution: Release w/ initalized caches, ie. initialize caches while building NBure
Tracked as IZ 106796
Open issues: Minor - how to build the cache in d/l build - depends on BE IZ 109115

For example install 2 modules from Ruby feature individually, rest of modules are not installed
Problem: Ruby is not present in Installed tab but in New plugins only
Solution: don't force all modules be installed to order to show in Installed
Tracked as IZ 106799 Done.
Open issues (still open): UI - how to present partially installed? (different rendering?) Where should be rest of feature? (in New plugin or Update plugins?)
Tracked as IZ 108677

Problem: The 'Web and J2EE' component contains Blueprints or other samples which are not searchable because are not in plugin description not display name of included modules
Solution: improve description of Web and J2EE to contain all meaningful words or concatenate all module's descriptions at the end of plugin description
Tracked as: IZ 106000

Problem: Mobility team thinks that their users will not be able to find SDKs among the other plugins
Tracked as: IZ 107999

Problem: library eg. Schliemann should be publish on UC but must be available for download if another plugin requires it
Solution:

S1: hide all eager/autoload modules in Plugin Manager, forbid browse modules like this
S2: group all module which which would like to hide to a special category (eg. Libraries or hidden) and don't expose these modules in Plugin Manager
S3: add a new one attribute in NBM descriptor what can hide corresponding modules

Problem: 3rd parties are used to publish own NBMs but there is no support/guide to publish features
Solution: improve 'suite.nbms' ant-task on Module Suite to generate Update Center descriptor for all suite modules w/ feature containing whole suite

Improve only for NB6 harness, for NB5.x harness it works as before (already proposed on dev@apisupport mailing list)
Write a guide for external developers, ask Geertjan for a help

Problem: Install IDE component into shared dirs which can be R/O for common user
Solution: Native support ?
Tracked as: TBD
Open issues: Many - depends on native support - differs by OS distribution, no UI support yet

Problem: some plugins (eg. JRuby) needs executable permission to be set but Autoupdate infrastructure doesn't support such feature
Open issue: How to describe mapping file<->permission
Tracked as: IZ 24357

Problem: PM shows only features
Solution: All modules which doesn't belong to any feature will tracked as standalone modules together w/ features
Tracked as IZ 106798
Note: Fixed in main trunk.
Open issues: None

JR04: Losing installed features between dev builds P2 in M10, P2 in NB6 Done.

Problem: Feature declaration contains list of depending modules w/ its version, If a module in IDE is older then declared dep. then is indicated as not installed
Solution: Handle features like this as partly installed feature
Open issues: as JR03

Problem: I prefer doing shared installs (ie, into my NB distribution, not userdir). When I do this with cnd it goes into the NB6.0 cluster rather than the cnd1 cluster.
Solution: Store the cluster name in the UC and install into the correct cluster
I can file an IZ if desired

\
\ Comments? More open issues?
\