Bug 798117

Summary:	Visualvm does not have correct directory structure to be supported in NetBeans
Product:	[Fedora] Fedora	Reporter:	James Livingston <jlivings>
Component:	visualvm	Assignee:	jiri vanek <jvanek>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	dbhole, joallen, jvanek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-25 09:17:54 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description James Livingston 2012-02-28 05:22:59 UTC

The visualvm package uses the "visualvm" and "profiler" directories under /usr/lib64/visualvm/ to store it's files, and depends on the netbeans-platform to provide the underlying platform (/usr/share/netbeans/platform12)

While that works for running visualvm, it means that NetBeans can't detect it correctly to add support as a new Platform for developing against, for example if you want to write a VisualVM plugin.


It doesn't detect it correctly because there is not platform installation in /usr/lib64/visualvm/. This can easily be fixed by adding a symlink for /usr/share/netbeans/platform12 as /usr/lib64/visualvm/platform, which fixes the problem for me.


To test, run Netbeans and use Tools->NetBeans Platforms, click Add Platform and navigate to /usr/lib64/visualvm. Netbeans should automatically populate the platform name with VisualVM 1.3.2 (or whatever version you have).