| << Back to previous view |
|
[QB-536] Some types of warnings are interpreted as errors
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | AlSt | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: | PMEase QuickBuild, 2.1.10, 2010-02-19 | ||
| File Attachments: |
build-log.txt
|
| Description |
|
Some types of warnings are interpreted as errors:
- deprecation warnings - "no such file" warnings - unchecked or unsafe operations See attached build log for details... |
| Comments |
| Comment by AlSt [ 19/Feb/10 01:40 PM ] |
| Sorry, this refers to the feature "Task and compilation error in Ant build step can now be catched and reported in build overview screen." |
| Comment by Robin Shen [ 20/Feb/10 04:09 AM ] |
| Unfortunately there is no obvious mark javac task output to distinguish errors and warnings (simply checking against words such as "warning" and "note" is not feasible since these words are different across different languages). We thought to mark all the errors and warnings produced by "javac" task as WARN instead ERROR. What do you think? |
| Comment by Robin Shen [ 23/Feb/10 05:41 AM ] |
| Errors now displayed as warnings in 2.1.11 |