| Summary: | build.properties problems should be reported one by one | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Dani Megert <daniel_megert> | ||||||||
| Component: | UI | Assignee: | Ankur Sharma <ankur_sharma> | ||||||||
| Status: | VERIFIED FIXED | QA Contact: | |||||||||
| Severity: | normal | ||||||||||
| Priority: | P3 | CC: | ankur_sharma, curtis.windatt.public, darin.eclipse | ||||||||
| Version: | 3.6 | ||||||||||
| Target Milestone: | 3.6 M7 | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | Windows 7 | ||||||||||
| Whiteboard: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Dani Megert
It shouldn't be hard to report separate problems, but I am not sure how nicely they will show up in the UI. I don't think it will be helpful if the user sees a problem, runs the quickfix, leaving another problem, and has to run the quickfix again. I would expect most users to just want to have the source issues fixed in one step. If we don't separate the problems we'll fix the text. > leaving another problem, and has to run the quickfix again.
Well, in my particular case I can only get rid of one problem because the other source folder contains initial "source" from which we build a JAR file that's then part of the binary bundle. Hence a combined quick fix would do the wrong thing. In JDT we never fix more than one problem at once. To fix several problems of the same kind the user has to do hit Ctrl+Enter to indicate he wants to fix all of them.
Moving to M7. Created attachment 163312 [details]
Patch
Created attachment 163313 [details]
updated test cases
Created attachment 163440 [details]
Final Patch
Fixed in HEAD Verified in N20100330-2000. |