Bug 197037 - [adopter breakage scan] Inconsistent results running adopter breakage on multiple plug-ins
Summary: [adopter breakage scan] Inconsistent results running adopter breakage on mult...
Status: RESOLVED WONTFIX
Alias: None
Product: WTP Releng
Classification: WebTools
Component: releng (show other bugs)
Version: 3.10   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Kaloyan Raev CLA
QA Contact: David Williams CLA
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-07-18 17:13 EDT by John Lanuti CLA
Modified: 2018-06-29 15:10 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 John Lanuti CLA 2007-07-18 17:13:45 EDT
If you are in a workspace making a possibly breaking change to adopters, and you select multiple plug-ins and run the scan for adopter breakages, if the last plug-in scanned runs clean, then the results come back clean even if there were errors in previous plug-ins.
Comment 1 David Williams CLA 2007-12-19 04:29:40 EST
Any interest/ability to handle this entry? 

(If not, you can assign back to me, and I'll decide if it would remain open, or closed as 'wont fix' ... or, maybe, "help wanted"). 

Thanks, 

Comment 2 David Williams CLA 2008-04-18 09:22:14 EDT
I suspect we should close as "won't fix", unless we can find someone to work on these tools. 

Comment 3 Kaloyan Raev CLA 2008-05-09 10:38:03 EDT
I think we should keep all valid bugs and enhancements open as long as the tool is "in use" and not deprecated. 

The "helpwanted" keyword and no target milestone seems to be enough markup for people to know that this is not planned to be fixed soon. 

I understand the WONTFIX resolution like "we acknowledge the problem, but we won't fix it because fixing it will cause bigger problem, e.g. break compatibility or adopters". I think this bug is not in this case. 
Comment 4 David Williams CLA 2009-10-01 21:18:42 EDT
How about we close "adapter scan" bugs as won't fix. Please reopen if you really plan to do anything here, but otherwise, I'd assume we'd want to do more with PDE's new API tools.