Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » Java Development Tools (JDT) » Forced to set project specific settings
Forced to set project specific settings [message #991030] Mon, 17 December 2012 01:44 Go to next message
Pierre-Yves Benzaken is currently offline Pierre-Yves Benzaken
Messages: 3
Registered: December 2012
Junior Member
Hi everyone,

I have following problem:

Since I migrated my projects from Eclipse 3.7.2 to Eclipse 4.2, I am forced to enable project specific compiler settings.

The only installed JRE within Eclipse is a 1.6.0 JDK and in the preferences the compiler compliance level is set to 1.6.

Still, all java projects containing java 1.5 specific language extensions, like static imports, don't compile any longer. I have to edit the properties of each project invidually and set the compiler compliance level to 1.6 by activating project specific settings. After that, I have to clean my project and it will compile successfully.

Anyone knows whether this is a known bug?

Any help would be appreciated Smile

P-Y
Re: Forced to set project specific settings [message #991093 is a reply to message #991030] Mon, 17 December 2012 05:41 Go to previous messageGo to next message
Dani Megert is currently offline Dani Megert
Messages: 3801
Registered: July 2009
Senior Member
On 17.12.2012 11:36, Pierre-Yves Benzaken wrote:
> Hi everyone,
>
> I have following problem:
>
> Since I migrated my projects from Eclipse 3.7.2 to Eclipse 4.2, I am
> forced to enable project specific compiler settings.
>
> The only installed JRE within Eclipse is a 1.6.0 JDK and in the
> preferences the compiler compliance level is set to 1.6.
Eclipse does not come with an installed JRE. You specify the JRE. In an
empty workspace that JRE is installed and used by default but you can
add additional JREs on the Java > Installed JREs preference page and you
can also specify the compiler compliance default on the Java > Compiler
preference page. Note though, that it is recommended to set those things
on your projects, e.g. to ease sharing them with others.

Dani
>
> Still, all java projects containing java 1.5 specific language
> extensions, like static imports, don't compile any longer. I have to
> edit the properties of each project invidually and set the compiler
> compliance level to 1.6 by activating project specific settings. After
> that, I have to clean my project and it will compile successfully.
>
> Anyone knows whether this is a known bug?
>
> Any help would be appreciated :)
>
> P-Y
Re: Forced to set project specific settings [message #991103 is a reply to message #991093] Mon, 17 December 2012 06:24 Go to previous messageGo to next message
Pierre-Yves Benzaken is currently offline Pierre-Yves Benzaken
Messages: 3
Registered: December 2012
Junior Member
Hi Dani,

Thanks for your answer. Unfortunately it looks like I wasn't really clear enough Wink

I added the JRE and set the compiler settings correctly. And this a long time ago! My point is only that, while working with Eclipse 3.x, I never had problems, and now with Eclipse 4.2, it looks like the compiler settings (those from the preferences) are totally ignored and I have to set them on each project.

Even if, as you are stating, this might be desired in order to ease sharing, this is not what I want!

P-Y
Re: Forced to set project specific settings [message #991130 is a reply to message #991103] Mon, 17 December 2012 07:49 Go to previous messageGo to next message
Dani Megert is currently offline Dani Megert
Messages: 3801
Registered: July 2009
Senior Member
On 17.12.2012 12:24, Pierre-Yves Benzaken wrote:
> Hi Dani,
>
> Thanks for your answer. Unfortunately it looks like I wasn't really
> clear enough ;)
>
> I added the JRE and set the compiler settings correctly. And this a
> long time ago! My point is only that, while working with Eclipse 3.x,
> I never had problems, and now with Eclipse 4.2, it looks like the
> compiler settings (those from the preferences) are totally ignored and
> I have to set them on each project.
We've never seen this. If you have self-contained reproducible steps,
then please file a bug against JDT UI.

Dani
>
> Even if, as you are stating, this might be desired in order to ease
> sharing, this is not what I want!
>
> P-Y
Re: Forced to set project specific settings [message #991139 is a reply to message #991130] Mon, 17 December 2012 08:16 Go to previous message
Pierre-Yves Benzaken is currently offline Pierre-Yves Benzaken
Messages: 3
Registered: December 2012
Junior Member
I don't. I just made a fresh new workspace and checked out my java projects out of CVS. These projects were previously maintained by developpers using Eclipse 3.6 / 3.7. I'll still try to make it reproductible...

P-Y
Previous Topic:"Open Call Hierarchy" can not work proper
Next Topic:How to analyse the runtime of my java programm
Goto Forum:
  


Current Time: Mon Sep 01 09:57:57 EDT 2014

Powered by FUDForum. Page generated in 0.02914 seconds