Bug 327036 - Some Ant tasks perform complete analysis instead of scoped analysis
Summary: Some Ant tasks perform complete analysis instead of scoped analysis
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: API Tools (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Vikas Chandra CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: investigate
Depends on:
Blocks:
 
Reported: 2010-10-05 15:37 EDT by Darin Wright CLA
Modified: 2023-02-03 16:14 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darin Wright CLA 2010-10-05 15:37:05 EDT 
Include/Exclude list support has been added to all the API Tools Ant tasks. Looking at the implementation of the tasks, I noticed that some tasks do a complete analysis and only apply the scope (included/excluded list) when generating XML. The tasks would be more efficient if they only analyzed the desired scope rather than filtering the result.

The following tasks do a complete analysis and filter the result:

* API Analysis Task
* API Freeze Task
* API Deprecation Task

The following tasks do a scoped analysis:

* API Use Task
* API Migration Task
* API Compare Task

It would be good to standardize on performing scoped analysis. For example, the Use and Compare tasks build an IApiScope and pass it into the analysis.
Comment 1 Eclipse Genie CLA 2019-02-21 10:45:56 EST 
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.
Comment 2 Dani Megert CLA 2019-02-21 11:08:29 EST 
Vikas, please check whether this is still valid.
Comment 3 Eclipse Genie CLA 2021-02-12 09:23:19 EST 
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.
Comment 4 Eclipse Genie CLA 2023-02-03 16:14:13 EST 
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.