how do we compare in our standard
settings? Some thoughts
- Do all our projects have the right
settings (including things in the incubator)?
- Would it be good to have a template
project settings file or steps that we can use for new projects that we
create? It seems like this is happening often (especially in the
- Some time ago we were considering
updating our coding standard to use explicit imports (rather than foo.*).
If we are going to do it, now is the time.
- At some point before we ship we should
format and organize imports on ALL projects
----- Forwarded by Jeff
McAffer/Ottawa/IBM on 02/23/2006 02:41 AM -----
Philippe P Mulet <philippe_mulet@xxxxxxxxxx> Sent by: eclipse-dev-bounces@xxxxxxxxxxx
02/22/2006 11:03 AM
Please respond to
"General development mailing list of the Eclipse project."
[eclipse-dev] Minimal compiler
severity for the Eclipse project
It appears that not all teams are tuning the compiler
settings in a similar
way, resulting sometimes in a few glitches during the build process. During
the arch call, we agreed that teams should ensure they follow the settings
used by Releng during the build process at a minimum.
Then we can discuss further on whether we want to raise the bar or not.
the compiler owner, I wouldn't change its defaults but rather have dev
teams agree on custom settings; since changing defaults has some
implications for tools generating source code; i.e. they could start
getting flagged with problems from now on.
To initiate the discussion, here are the extra warnings we activate in
JDT/Core (compared to defaults).
- Inline finally blocks: ON (to match Releng setting for improved
- Indirect access to static member
- Undocumented empty block
- Non externalized Strings
Name shadowing and conflicts
- Field declaration hides another field or variable
- Local variable declaration hides another field or variable
Deprecated and restricted API
- Deprecated API
- Forbidden reference (ERROR)
- Discouraged reference
- Unnecessary cast or 'instanceof' operation
- Malformed Javadoc comments: Warning
- Only consider members as visible as: Private
- Report errors in tags: ON
- Report non visible references: ON
- Report deprecated references: ON
You can find below the corresponding .settings/org.eclipse.jdt.core.prefs
(you can simply paste the contents into your project settings to see the
consequences if you cause a rebuild, i.e. no need to go through the UI).
eclipse-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit