Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346878 - Make compare to API Baseline wizard easier to find
Summary: Make compare to API Baseline wizard easier to find
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: API Tools (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE API Tools Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on: 274560
Blocks:
  Show dependency tree
 
Reported: 2011-05-23 11:26 EDT by Curtis Windatt CLA
Modified: 2019-09-08 12:11 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Curtis Windatt CLA 2011-05-23 11:26:03 EDT
I found testing bug 346686 difficult to test as finding and opening a session in the API Tools view is difficult.

Possible suggestions:
1) Put the API Tools view in with the rest of the PDE views instead of its own category.

2) When the API Tools view is opened with no session, have some default text that says to select one or more projects and open 'compare to > API Baseline'

3) Update the doc to say where the menu option is and that it will only show up if api tooling enabled bundles are selected (selecting just one test/releng/etc. removes the option from the menu).

4) Consider moving the compare action out of the compare to submenu and in with the PDE Tools menu beside API Tools Setup.
Comment 1 Dani Megert CLA 2011-05-25 03:29:50 EDT
Even bigger problem: the Compare With > API Baseline... context menu item is not there until the API Tools UI bundle got loaded and that normally never happens unless one actively opens the view or goes to one of the preference pages.
Comment 2 Dani Megert CLA 2011-05-25 03:30:56 EDT
And it's missing in the Project Explorer (bug 274560).
Comment 3 Eclipse Genie CLA 2019-09-08 12:11:31 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.