Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 289139 - Allow to override/specify internal/API package name patterns in API use scan
Summary: Allow to override/specify internal/API package name patterns in API use scan
Status: VERIFIED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: API Tools (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: 3.6 M2   Edit
Assignee: Darin Wright CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 288557
Blocks:
  Show dependency tree
 
Reported: 2009-09-10 15:35 EDT by Darin Wright CLA
Modified: 2010-01-20 14:35 EST (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 Darin Wright CLA 2009-09-10 15:35:43 EDT
Some projects do not use API tooling (i.e. projects are not configured to use API tooling in the IDE). Some projects export all their internal packages without using the x-internal modifier (to identify internal packages). In such cases, all packages of a bundle are seen as API, when in fact the .internal packages are intended to be non-API.

We should consider this case when initializing an API description for a bundle (i.e. no API description and no x-internal modifiers and .internal package names exist).
Comment 1 Darin Wright CLA 2009-09-11 13:32:46 EDT
Instead, added more generic function in the use scan to allow internal and API package names to be specified as regular expressions. Released inital infrastructure to HEAD. Need to update Ant task and add UI.
Comment 2 Darin Wright CLA 2009-09-11 14:52:24 EDT
Updated Ant task to allow for new arguments: apipatterns and internalpatterns
Comment 3 Michael Rennie CLA 2009-09-11 16:32:01 EDT
UI code has been committed
Comment 4 Darin Wright CLA 2009-09-14 14:07:20 EDT
Fixed in M2. Will open new bugs as required.
Comment 5 Darin Wright CLA 2009-09-14 14:07:29 EDT
Verified.