Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 313158

Summary:	[Helios] Provide capability/activity definitions
Product:	[Tools] Linux Tools	Reporter:	Andrew Overholt <overholt>
Component:	Project	Assignee:	Andrew Overholt <overholt>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	charley.wang, linux.distros-inbox, rgrunber
Version:	unspecified
Target Milestone:	0.6
Hardware:	PC
OS:	Linux
Whiteboard:

Description Andrew Overholt

2010-05-17 11:09:09 EDT

According to the Helios simultaneous release requirements, we must:

"... provide basic capability/activity definitions to allow for their UI contributions to be hidden. These may be provided in a separate plugins and features to facilitate inclusion and reuse by consumers in product development, or simply well documented so adopters can reuse via copy/paste. Ideally, projects should also provide triggers to facilitate progressive discovery of functionality."

Once they're available, I will add a URL to the description of and documentation for such plugins in the portal.

Comment 1 Andrew Overholt

2010-05-18 13:51:42 EDT

Roland or Charley:  can you see what's required here?  Thanks.

Comment 2 Roland Grunberg

2010-05-18 15:13:29 EDT

This is being used to manage the UI of many plug-ins that provide similar functionality. In the context of 'linux tools project', I think this would maybe entail adding an activity for "profile as", and making sure that callgraph,oprofile,valgrind,etc UIs are listed.

Comment 3 Charley Wang

2010-05-18 16:59:23 EDT

(In reply to comment #1)
> Roland or Charley:  can you see what's required here?  Thanks.


Roland and I took a look at capabilities. We've added a org.eclipse.linuxtools.profiling.ui.capability to the Trunk.

This project will blanket-disable all UI contributions from:

Gprof
Gcov
Lttng
Tmf
Callgraph
SystemTap GUI/Dashboard
Valgrind
OProfile

This project should NEVER be included in a build/distribution or users will become very confused.

Should we move it elsewhere/take steps to ensure it does not get added?

Comment 4 Charley Wang

2010-05-18 16:59:38 EDT

Documentation is at: http://wiki.eclipse.org/Linux_Tools_Capabilities_Helios

Comment 5 Andrew Overholt

2010-05-18 17:29:03 EDT

Thanks, guys.  I think we should also have a plugin to disable all UI contributions from autotools, ChangeLog, RPM, etc.

Comment 6 Charley Wang

2010-05-18 18:09:24 EDT

(In reply to comment #5)
> Thanks, guys.  I think we should also have a plugin to disable all UI
> contributions from autotools, ChangeLog, RPM, etc.

Sure -- we'll also look at setting the default enablement for these capability plugins so they can be included in the update site.

Comment 7 Charley Wang

2010-05-19 11:33:50 EDT

(In reply to comment #6)
> (In reply to comment #5)
> > Thanks, guys.  I think we should also have a plugin to disable all UI
> > contributions from autotools, ChangeLog, RPM, etc.
> 

Note: I've modified the org.eclipse.linuxtools.profiling.ui.capabilities to default to on, we can probably safely include it in builds now to give users the ability to turn it on/off through the Capabilities Preferences page.

Comment 8 Charley Wang

2010-05-19 14:07:08 EDT

Capabilities plugins have been created for Linux Tools projects and documented here:

http://wiki.eclipse.org/Linux_Tools_Capabilities_Helios#Introduction

I've set this URL into our Helios Simultaneous Release tracker.

Comment 9 Andrew Overholt

2010-05-31 14:36:49 EDT

This is done.  Thanks, Charley and Roland.