On which version of Java are you running Eclipse with Spring IDE?

[Torsten Juergeleit]

For Spring IDE version 2.0 we would like to leverage the new language features of Java 5 (mostly generics, foreach loops and enums). Now we are wondering how many Spring IDE users are still running Eclipse on Java 1.4 and why.

Torsten

[mraible]

I've recently starting switching all my open source projects to Java 5.

+1 to JDK 5.

For projects requiring 1.4 compilation, there's always Retroweaver (http://retroweaver.sourceforge.net).

[Dave Syer]

I use both 1.5 and 1.4 in projects (so I voted for 1.4). Unfortunately the big container vendors are still on 1.4, so it isn't practical for people who use or might have to use (e.g.) WebSphere to switch to 1.5 yet.

I guess maybe that doesn't mean I can't use Java 5 to run Eclipse and Spring IDE? Maybe I should vote again...

[betabagel]

Unfortunately the big container vendors are still on 1.4, so it isn't practical for people who use or might have to use (e.g.) WebSphere to switch to 1.5 yet.

Exactly the same problem here. Company politics has made upgrading Websphere servers a slow process. Actually we are now migrating from 1.3 to 1.4

[kantorn]

Exactly the same problem here. Company politics has made upgrading Websphere servers a slow process. Actually we are now migrating from 1.3 to 1.4

Same problem here. WebSphere and its mothership IBM is well-known for letargic processes implementing new JDK:s....
I'm one of the guys getting a bit worried about a too quick pace in adding features to Java.... I mean Java 5 has great values such as templates... but Java 6 is already here and 7 is around the corner making Java look more and more like a scripting language.... but the big vendors doesn't keep up the pace. Beginning to wonder if all the adds to the Java spec is really necessary.
One of the really big arguments for Java is its fantastic open-source products, but all the new Java versions increase the risk of incompabilities and thus decreased usability to companies etc. I'm not at all a fan of M$ and .NET (just compare Java's 25 keywords to C# which at least doubles that) but colleauges that like it says "At least the products work together" Of course they do; one vendor - one version. One of the major downsides of Java development is incompabilities between versions and tendency to "Jarmaggedon"-experiences.
Just thinking aloud....

[ronwheeler]

Same problem here. WebSphere and its mothership IBM is well-known for letargic processes implementing new JDK:s....
I'm one of the guys getting a bit worried about a too quick pace in adding features to Java.... I mean Java 5 has great values such as templates... but Java 6 is already here and 7 is around the corner making Java look more and more like a scripting language.... but the big vendors doesn't keep up the pace. Beginning to wonder if all the adds to the Java spec is really necessary.

I agree.
I have been around a long time and most major languages have some stability. Java is starting to look like an inside the beltway, script kiddies language where marginally useful features are added just to satisfy the egos and intellectual curiousity of the developers.
The grownups need to step in and put some discipline into the process.
The language should be stablized until the user community starts screaming for new features.
Five years between major versions is a decent interval for a language of the maturity of Java. This would give an incentive for major vendors and projects to upgrade. With the current speed of new versions, it is dificult to start an upgrade from 1.4.2 since as soon as you start and get partway through the process, you will have to switch target versions. I am sure that they are thinking that they might as well wait for Java to stablize.
A stable version would also give an incentive to writers and educators to document and promote a current version. This would help in getting the new features more widely used and understood.
The effort expended on new versions could be spent on performance, documentation and tools.
I would like to know what program can not be written in Java 6 that will be possible with Java 7.
I would like to see compelling examples of code that is going to be so much more efficient under Java 7.
If there are insufficient examples then put off the release of Java7 until 2011 and let the community absorb Java 6 and start to build a user-driven set of requests for new features for Java 7. I do not have any. Anyone else see defficiencies in Java 6's specification that is going to stop them from working?

[Marten Deinum]

+1 for Java 5 here also.

We are also currently in the process of switching our internal project to Java 5.

[salp]

I voted for 1.5, but that's because I'm in the luxurious position that the Java development here is a green field, all legacy systems are in a different language.
All new projects I start in 1.5, I'm migrating some old ones from 1.4 to 1.5

But... I know a few old clients of mine that have no choice then to run 1.4 (and even a few still have to run 1.3), no way around it.

[Andreas Senft]

Actually I'm running Eclipse with Java 5 (but in 1.4 compatibility mode) and run the application with a 1.4.2 JRE as we too have a restriction based on the app server.

But in this scenario I think I can vote for Java 5 :-)

[karldmoore]

I voted for 1.5, but that's because I'm in the luxurious position that the Java development here is a green field, all legacy systems are in a different language.
All new projects I start in 1.5, I'm migrating some old ones from 1.4 to 1.5

But... I know a few old clients of mine that have no choice then to run 1.4 (and even a few still have to run 1.3), no way around it.

We are in the same position regarding 1.5, very nice!

Some of our agent code however has to be 1.1 compatible, . Thats so last century , where was I in 1997?