Wednesday, March 08, 2006
Eclipse 3.2 M5 brings the addition of a new supported SuppressWarnings annotation parameter: 'restriction'. This new annotation allows you to tell the Eclipse JDT compiler to stop nagging you about something naughty you are doing in your code, such as referencing an 'internal' package in your Eclipse plug-in, or perhaps your project has access rules defined, as I described previously here . These access rules and definitions exist for a reason; to warn you if you are breaking rules. That being said, sometimes breaking rules is neccessary; and in those cases it's nice to be able to tell Eclipse to keep it's mouth shut
Posted by Col at 6:16 am
- Yahoo! Mail: Revenge of the Oddpost
- Creating an as400 Query
- Free Iseries Accounts Available
- How do you re-enable the user id for STRSST when it has been disabled?
- Javalobby - Java J2EE Programming Forums - Coldtags suite 2.1: 210+ custom JSP tags
- What is QZHQSSRV job?
- AS400 / ISeries Freeware / Shareware
- AS400 PRTF - Report Layout Utility
- Other as400 tips sites
- AS400 Job Scheduler