[#QB-536] Some types of warnings are interpreted as errors

QuickBuild

Some types of warnings are interpreted as errors

Created: 19/Feb/10 01:16 PM Updated: 23/Feb/10 05:41 AM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

None

Original Estimate:	Unknown	Remaining Estimate:	Unknown	Time Spent:	Unknown
File Attachments:	1. build-log.txt (2 kb)
Environment:	PMEase QuickBuild, 2.1.10, 2010-02-19

Description

« Hide

Some types of warnings are interpreted as errors:
- deprecation warnings
- "no such file" warnings
- unchecked or unsafe operations

See attached build log for details...

All

Comments

Work Log

Change History

Sort Order:

Change by AlSt [19/Feb/10 01:16 PM]
Field	Original Value	New Value
Attachment		build-log.txt [ 10155 ]

[ Permlink | « Hide ]

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."

[ Permlink | « Hide ]

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?

[ Permlink | « Hide ]

Robin Shen [23/Feb/10 05:41 AM]

Errors now displayed as warnings in 2.1.11

Change by Robin Shen [23/Feb/10 05:41 AM]
Status	Open [ 1 ]	Resolved [ 5 ]
Resolution		Fixed [ 1 ]