Even though this way we only find those Eclipse Java projects that
use project specific settings...
Is there a possibility to ask someone at GitHub to "grep" all
occurrences of "org.eclipse.jdt.core.compiler.problem
extension:prefs" and send us the result as text file (~190.000
Then we could do a simple analysis for each individual setting.
Am 27.11.2013 15:34, schrieb Sven
In order to find out what settings
people use today we could query github (and alike).
I did that for the compiler option "Boxing and unboxing
At github that option is set 14,244 times to ignore  (today's
default), and only 1,061 to warning  (the proposal)
and 230 to error .
I don't think everyone sets her/his compiler settings
carefully, but the available data on github could help us
identifying the compiler options
which differ from the default settings mostly. Same with
other Eclipse settings.
 - https://github.com/search?q=org.eclipse.jdt.core.compiler.problem.autoboxing%3Derror&type=Code&ref=searchresults
I’m late to the party here, so rather than
skimming through the entire thread let me just ask
Has it been
considered to provide preconfigured “Warning
Profiles” with 3 simple levels (picky, standard,
I see two
big workflows here:
(a) I’m stuck
with a big pile of legacy code, please don’t
defocus my attention with lots of unnecessary
(b) I’m writing
some new code, please give me picky warnings to
help me write clean code.
experience, the real annoyance is having to deal
with each warning individually, and that on a
global scope. I see some warning in the Problems
view, what the heck is the right entry in
Preferences to turn that beast off ?
tool would be intelligent enough to know what
files I have touched with new code (and enable
picky warnings on those files before I checkin),
but leave the old code alone without extra
warnings unless I ask for them.
what the outcome of the survey will be, but IMO
there is no “one size fits most” approach to the
to make it easier fit a user’s situation (type a
or type b, and allow easy turn-off of individual
warnings that annoy me).
investing too much into a good single default.
Martin Oberhuber, SMTS /
Product Architect – Development Tools, Wind
+43.662.457915.85 fax +43.662.457915.6
survey asking about line numbers and compiler
warnings is now live. We will be promoting it on eclipse.org
and the usual social media channels. Feel free to
help promote it. The survey will end in 2 weeks.
ide-dev mailing list
ide-dev mailing list