Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ide-dev] Survey for IDE feature enhancements

"More aggressively" is quite vague but IMHO much better than the initial question.
When you say "potential programming problems"  do you refer to just that subsection in warnings/errors?

Also if we do the survey with that question and people vote for "Yes" we'll have to answer the next question:
Which of the currently ignored checks should be switched to a warning?


On Nov 20, 2013, at 10:26 AM, Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx> wrote:


Assuming those are defaults we can change at the EPP level, I volunteer for implementing them.

However, may I propose to re-phrase the question as follows:

Questions: Java Compiler Warnings
The Eclipse Java compiler performs additional code analysis in order to detect potential programming problems. For some of the problems, convenient Quick Fixes are available to easily correct them. Currently, only a few of those will be reported as warnings by the compiler. It is possible to configure each of them via the Eclipse preference settings.

Some users have requested that the compile more aggressively reports programming problems by default. This will likely result in more compile warning being reported for your Java code edited in Eclipse.

To serve our users best, we would like to know what the majority of the users desires. Therefore please vote based on your preference. 

The Eclipse IDE should report potential programming problems in Java source code more aggressively by default: 

1.) Yes 
2.) No

IMHO this follows the style of the previous question and leaves flexibility to not turn on experimental options by default and/or to turn on future options by default.


Am 20.11.2013 um 10:12 schrieb Ian Skerrett <ian.skerrett@xxxxxxxxxxx>:

I am fine asking this question but how will it get implemented? Is there a committer ready to accept a patch that will make it into Luna?
From: ide-dev-bounces@xxxxxxxxxxx [mailto:ide-dev-bounces@xxxxxxxxxxx] On Behalf Of Mickael Istria
Sent: November-19-13 3:12 PM
To: ide-dev@xxxxxxxxxxx
Subject: Re: [ide-dev] Survey for IDE feature enhancements

Line numbers are indeed a good first question.
I'd like to add one about Warnings:

Enable static analysis warnings?
JDT and other language tools provides powerful static analysis to detect bad practices and suggest fixes. Most of those rules are ignored by default. Those rules are already visisble in Eclipse IDE, under Preferences > Java > Compiler > Errors/Warnings. Which of the following behaviour would you prefer:
* Keep rules enabled as it is now (some are turned on, some are not)
* Show all available broken rules in your code as warnings (more warnings/hits reported, some rules may not be relevant to your use-case and would require you to explicitly disable them in Preferences)

Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets
ide-dev mailing list

Gunnar Wagenknecht

ide-dev mailing list

Back to the top