Community
Participate
Working Groups
Provide a user interface for creating API use scans. The UI should provide flexibility to: * analyze an API baseline, target platform, or the workspace * specify the source scope to be searched (i.e. where to extract references from) * specify the target scope of interest (i.e. only collect references to specific things) * limit the scan to API and/or internal references Source/target scopes could be an entire baseline, or a specific set of bundles within the baseline. We also need to consider other ways of grouping bundles to make it simpler to specify searches like "find all references between WTP and the SDK". For example, we might consider features.
Additionally, the UI could specify to generate XML/HTML reports or show results in the search view. However, showing results in the search view will inevitably make users want to see attached source.
Created attachment 144689 [details] work in progress This patch is the initial works from Darin (from our internal update site). This approach uses an external tools launch configuration type for launching the tooling.
committed the first draft of the UI (not released for the I build though)
applied latest enhancements to HEAD. The UI now allows you to search a baseline, target definintion, or the workspace + target and uses Java regular expressions to define the search scopes. please verify Darin W
.
I removed the "workspace" option, as it does not seem like a typical use case. I also changed the "installation" option to work as a directory of bundles, rather than an "install". I think this will be a more common scenario.
