Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » Java Development Tools (JDT) » Project-specific Compiler Warning Settings
Project-specific Compiler Warning Settings [message #1279308] Fri, 28 March 2014 14:56 Go to next message
Chris Barlock is currently offline Chris Barlock
Messages: 15
Registered: July 2009
Junior Member
Some time ago, I configured project-specific settings for the Java Compiler Errors/Warnings. This generated a .settings/org.eclipse.jdt.core.prefs files, which is now part of our source code so that all the developers have a copy. However, I'm told that some of the warnings I see, others do not. (One happens to be a try-with-resource warning. I checked with one of the developers and her compiler compliance level was set to 1.7 and she is using a Java 7 SDK.)

Is there something else that has to be set in each developers workspace to enable the project-specific settings, or should the existence of .settings/org.eclipse.jdt.core.prefs be enough?

Thanks!

Chris
Re: Project-specific Compiler Warning Settings [message #1279376 is a reply to message #1279308] Fri, 28 March 2014 16:53 Go to previous messageGo to next message
Ed Merks is currently offline Ed Merks
Messages: 26137
Registered: July 2009
Senior Member
Chris,

Comments below.


On 28/03/2014 3:56 PM, Chris Barlock wrote:
> Some time ago, I configured project-specific settings for the Java
> Compiler Errors/Warnings.
How long ago?
> This generated a .settings/org.eclipse.jdt.core.prefs files, which is
> now part of our source code so that all the developers have a copy.
> However, I'm told that some of the warnings I see, others do not.
> (One happens to be a try-with-resource warning.
That sounds like a newer type of thing. Likely you don't have project
specific preferences for that...
> I checked with one of the developers and her compiler compliance
> level was set to 1.7 and she is using a Java 7 SDK.)
> Is there something else that has to be set in each developers
> workspace to enable the project-specific settings, or should the
> existence of .settings/org.eclipse.jdt.core.prefs be enough?
Existence should be enough, but keep in mind that JDT introduces new
warnings from release to release, and you won't have project specific
preferences for those new warnings...
>
> Thanks!
>
> Chris
Re: Project-specific Compiler Warning Settings [message #1279433 is a reply to message #1279376] Fri, 28 March 2014 18:52 Go to previous messageGo to next message
Chris Barlock is currently offline Chris Barlock
Messages: 15
Registered: July 2009
Junior Member
>How long ago?
Originally started last August, updated from time to time.

>That sounds like a newer type of thing. Likely you don't have project
>specific preferences for that...
It is new to Java 7, under Code style: Resource not managed via try-with-resource.

> Existence should be enough, but keep in mind that JDT introduces new
> warnings from release to release, and you won't have project specific
>preferences for those new warnings...
You will if I, say, periodically update the project-specific preferences, which I have been doing. If existence should be enough, I'll have to dig a little more into this.

Chris
Re: Project-specific Compiler Warning Settings [message #1279601 is a reply to message #1279433] Sat, 29 March 2014 01:05 Go to previous messageGo to next message
Chris Barlock is currently offline Chris Barlock
Messages: 15
Registered: July 2009
Junior Member
Looks like the issue is the version of Eclipse or the version of Eclipse that is the basis for the various RTC versions that different people on the team are using. Lack of consistency...bah!

Thank you, Ed!

Chris
Re: Project-specific Compiler Warning Settings [message #1279680 is a reply to message #1279601] Sat, 29 March 2014 04:13 Go to previous message
Ed Merks is currently offline Ed Merks
Messages: 26137
Registered: July 2009
Senior Member
Chris,

Consistent automated installations is something that Oomph is focused on:

https://wiki.eclipse.org/Eclipse_Oomph_Installer

The idea being that you provide a description of how the
project-specific IDE should be installed and provisioned so everyone
used it to end up with the same configured installation.

We've proposed a new project for it:

https://projects.eclipse.org/proposals/oomph

The tool set will include a tool to maintain consistent project-specific
preferences, i.e., you'll be able to change the project-specific
preferences in one project and they will propagate to all the other
appropriate projects (where appropriate is based on rules/predicates you
define)...

On 29/03/2014 2:05 AM, Chris Barlock wrote:
> Looks like the issue is the version of Eclipse or the version of
> Eclipse that is the basis for the various RTC versions that different
> people on the team are using. Lack of consistency...bah!
> Thank you, Ed!
>
> Chris
Previous Topic:Writing unit tests for JUnit launches
Next Topic:Missing Files?
Goto Forum:
  


Current Time: Thu Oct 23 06:52:16 GMT 2014

Powered by FUDForum. Page generated in 0.01960 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software