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 185587

Summary:	[69cat] Add an existing OSGi jar to the module suite
Product:	apisupport	Reporter:	abajja <abajja>
Component:	Project	Assignee:	Jaroslav Tulach <jtulach>
Status:	RESOLVED WONTFIX
Severity:	normal	CC:	anebuzelsky, jglick
Priority:	P4	Keywords:	UI
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	ENHANCEMENT	Exception Reporter:
Attachments:	illustartion

Description abajja 2010-05-06 08:00:41 UTC

[ JDK VERSION : 1.6.* ]

When you want to add a jar to your RCP application you have to do it by
means of library module, but for the OSGi bundle you must go to the suite >
properties > add cluster, etc., which is a long path for the user. It would be
desirable to add an action that abstracts all this from the user and it is more
intuitive (see illustration).

Comment 1 abajja 2010-05-06 08:04:28 UTC

Created attachment 98541 [details]
illustartion

Comment 2 Jesse Glick 2010-05-06 14:03:44 UTC

I guess such a menu item could create a new imported cluster containing just a single module? What would happen if you selected this menu item several times in a row - import to the same new cluster? Or should you be able to multiselect bundle JARs in the chooser? Needs some thought from the UI side. Definitely not for 6.9.

Comment 3 Jaroslav Tulach 2010-05-06 14:20:53 UTC

Flawed. Add a Library generates build scripts, etc. Nothing like that shall happen in case of OSGi. That is why we decided to support just "cluster import". 

The plan is at
http://wiki.netbeans.org/OSGiAndNetBeans
and
http://wiki.netbeans.org/OSGiAndNetBeansImportBundles

I don't see a way how to change the UI flow in foreseeable future for Ant based NetBeans Module Projects. Marking won'tfix. If you want more natural workflow, switch to Maven. It basically provides what you are asking for.

Comment 4 Jesse Glick 2010-05-06 14:25:42 UTC

I think you misinterpreted the request (though I can't be sure). Reporter knows that cluster import works for this case; it just more work to do it through the UI than it perhaps should be in the case that you only need to add one bundle. "Add Existing OSGi JAR" need not create a new project, just add an entry to the cluster path. It should not I guess be in the context menu item on Modules in this case however, as no new entry in Modules would appear after running it.

Comment 5 Jaroslav Tulach 2010-05-06 23:35:31 UTC

Shall the osgi.jar be copied somewhere or stay at current location? If copied, are you suggesting creation of a special "external" cluster which would contain all these JARs? What about type of this module (autoload probably), what if the user wants to change the type?

In short, I don't think this is ready for implementation. According to my treatment of bugs, I'll soon close as won'tfix.

On the other hand, I need to modify the build scripts for netbeans.org repository for post 6.9: I need to have an "external" cluster with OSGi binaries used in NetBeans IDE. Can you think about that, Jesse?

Comment 6 Jaroslav Tulach 2010-05-17 04:58:37 UTC

Marking won'tfix. The level of contribution from submitter is too low.