I agree that it would be benefitial to change these settings for Eclipse projects. However, I am uncomfortable doing this in a way that effects all users of Eclipse. If we feel that this is something we want to do, then one of our first steps in the next release should be to provide a mechanism by which organizations (such as Eclipse) can provide settings that are to be applied to their projects. I can see two vehicles for doing this.
- a set of sharable global preferences. This is similar to what we have now with preference import/export but would allow a subset of preferences to be shared.
- sharing of project properties in the repository. These compiler settings can be set for each project in Eclipse. If these could be shared with each project in the repository, then any developer working on the project would get the errors. (see bug http://bugs.eclipse.org/bugs/show_bug.cgi?id=34106)
I prefer the second option since it allows a developer to tailor the compiler settings for individual projects (which may follow different conventions).
Just my 2 cents worth
Olivier Thomann/Ottawa/IBM@IBMCA Sent by: eclipse-dev-admin@xxxxxxxxxxx
22/04/2003 10:42 AM
Please respond to eclipse-dev
Subject: [eclipse-dev] Compiler warnings
I think it is time to change the settings of the compiler for everyone. I
noticed new warnings in the latest nightly builds. They are mostly due to
unused imports. It might be a godd thing that everyone is using the
- unused import = ERROR
- unused locals = ERROR
- non static access to static member = ERROR
- assignment has no effect = ERROR
- Using a char array in string concatenation = ERROR
This might help to reduce the number of useless warnings. It took time to
get rid of them prior to 2.1 release. So we might want to change the
settings immediately and that should prevent us from chasing them right
before the next release.
eclipse-dev mailing list