Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 324474 - Directory option on API Use configuration should use installation
Summary: Directory option on API Use configuration should use installation
Status: VERIFIED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: API Tools (show other bugs)
Version: 3.7   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.7 M2   Edit
Assignee: PDE API Tools Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 322572
Blocks:
  Show dependency tree
 
Reported: 2010-09-03 14:30 EDT by Curtis Windatt CLA
Modified: 2011-01-26 14:24 EST (History)
2 users (show)

See Also:


Attachments
Possible fix (4.17 KB, patch)
2010-09-03 14:31 EDT, Curtis Windatt CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Curtis Windatt CLA 2010-09-03 14:30:03 EDT
The fix for bug 322572 will move the code that scans directories/installations into the api tooling core bundle.  The directory option on the launch config is the only place in api tooling where we explicitly scan a directory and not treat it as an installation.

If the behaviour needs to stay this way, we should add comments to the code and update the help doc to explicitly describe its behaviour (as it differs from the preference page).

If we can change the behaviour, we can either reuse the same code the preference page uses or delete the option entirely (if forcing the user to create a baseline or target definition on the preference page is not too onerous).
Comment 1 Curtis Windatt CLA 2010-09-03 14:31:23 EDT
Created attachment 178187 [details]
Possible fix

This fix changes the createBaseline method to use the code introduced in bug 322572.
Comment 2 Curtis Windatt CLA 2010-09-03 15:56:59 EDT
If we are changing the behaviour of the ant tasks, it makes sense to change the behaviour of the launch config.
Comment 3 Darin Wright CLA 2010-09-07 12:26:21 EDT
This was fixed with bug 322572.