Re: [jbosstools-dev] [i18n] NON-NLS warnings by module

On 06/05/2009 10:15 AM, Sean Flanigan wrote: [snip two useless suggestions] Oh. I've done a bit more reading. Apparently PDE Build ignores per-project settings [1]. Which I'm sure everyone else already knew. I suppose I had assumed that Eclipse had more integration between batch builds and IDE builds. Still, it looks as if enabling warnings on the build server should be pretty easy: we just have to set (eg) compilerArg=-warn:nls in build.properties. [2] That only leaves the problem of where all these warnings will end up. If we don't change anything else, I imagine they'll just end up in Hudson's console output. Even that would be a start, since we could just grep it for interesting warnings, count them, etc etc. Eventually, tracking compiler warnings the way PMD warnings are tracked might be nice. There's a plugin [3] that sounds pretty good for this. Sean. [1] http://wiki.eclipse.org/PDE/Build "PDE/Build does not know anything about the Java Builder settings in your workspace or on your project. Your plug-in's manifest.mf and build.properties files are the input to PDE/Build." [2] http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclipse.jdt.doc.isv... "Warning options" [3] http://wiki.hudson-ci.org/display/HUDSON/Warnings+Plugin -- Sean Flanigan Senior Software Engineer Engineering - Internationalisation Red Hat