Java5 back port… what should we include?

276 views
Skip to first unread message

Christian Gruber

unread,
Sep 25, 2012, 2:45:13 PM9/25/12
to guava-discuss
Hey all,

    Louis and I are rolling up the guava-jdk5-13.0 release, but there are a few things worth checking out.  In particular, does anyone need both jdk5 AND gwt from that JDK5 base.  In particular, are people rolling android/froyo and gwt libraries from the same source?  We can do it, and there's no real cost at this point, but since GWT is able to handle Java6 (modulo some things it hasn't learned to emulate yet) there's really no reason that we can see for maintaining a java5-gwt part of the back port.

    But, we don't want to screw people up here, so if you need Java5-compliant sources for GWT use, please speak up, so we can make sure we support you.

cheers,
Christian and the Guavians.

Raymond Rishty

unread,
Sep 25, 2012, 3:03:19 PM9/25/12
to Christian Gruber, guava-discuss
I don't see a problem with leaving GWT out of the backport. I use GWT, and I'm stuck on Java 5 for some things, but those tasks don't really intersect.


Gregory Kick

unread,
Sep 25, 2012, 3:23:32 PM9/25/12
to Raymond Rishty, Christian Gruber, guava-discuss
I thought that GWT didn't support Java 1.6 anyway and that we were doing some tricky things in the emulation to get rid of things like references to NavigableMap. Might we be better off building the GWT version from the backport since that's essentially what we've been doing in the emulation anyway?
--
Greg Kick
Java Core Libraries Team

Thomas Broyer

unread,
Sep 25, 2012, 3:24:17 PM9/25/12
to guava-...@googlegroups.com
FYI, GWT requires JDK6 since version 2.4 released a year ago.

Louis Wasserman

unread,
Sep 25, 2012, 3:26:08 PM9/25/12
to Thomas Broyer, guava-...@googlegroups.com
Yeah, but its JDK6 support isn't exactly complete -- most notably lacking the Navigable methods.

--



--
Louis Wasserman

Christian Gruber

unread,
Sep 25, 2012, 3:27:04 PM9/25/12
to Gregory Kick, Raymond Rishty, guava-discuss
Sort of.  The GWT team is taking our navigable map stuff so it'll work with everyone's code, not just Guava in the future.

Let me phrase it better.  People can use guava-gwt-13.0.jar for GWT development now in an environment that uses a JDK6 for building.  Do we need a guava-gwt-jdk5-13.0.jar, since people can, currently, use the other.  The value of that extra combo seems pretty sparse.  

Gregory Kick

unread,
Sep 25, 2012, 3:35:01 PM9/25/12
to Christian Gruber, Raymond Rishty, guava-discuss
So, whether or not GWT or GWT tooling or whatever supports/requires Java 1.6 or whatever (can't find anything that mentions it in https://developers.google.com/web-toolkit/release-notes) seems to be less important than the state of the JDK emulation, which seems to have changed very little.  (Even if the GWT team does it right now this instant, it's a long time until most people are on the latest version).

My point was that if the effort of the backport has significant overlap with the stuff that we're doing with GWT then it's probably worth seeing whether or not you can consolidate those efforts.  That then has the added bonus of the 1.5-compatible GWT release and the 1.6-compatible GWT release being the same thing.

All just conjecture, but maybe worth looking into. 

Christian Gruber

unread,
Sep 25, 2012, 4:50:15 PM9/25/12
to Gregory Kick, Raymond Rishty, guava-discuss
Yeah - they're sort of orthogonal, sadly, even if there is overlap.  In the case of GWT, we're largely pulling out things, and not doing a whole lot of emulation except for the navigable map stuff.  Mostly we're pulling GWT incompatible stuff out.  JDK emulation really belongs to the GWT team and they'll eventually absorb or re-work anything we do on that front.  

Thomas' comment about GWT having required Java6 since GWT-2.4 seems to make having a jdk5-gwt guava sort of a weird thing.  So I"m really only looking to release that if there are some good edge-cases that need it.  

Thomas Broyer

unread,
Sep 26, 2012, 2:51:16 AM9/26/12
to guava-...@googlegroups.com, Gregory Kick, Raymond Rishty


On Tuesday, September 25, 2012 10:50:20 PM UTC+2, Christian Gruber wrote:
Yeah - they're sort of orthogonal, sadly, even if there is overlap.  In the case of GWT, we're largely pulling out things, and not doing a whole lot of emulation except for the navigable map stuff.  Mostly we're pulling GWT incompatible stuff out.  JDK emulation really belongs to the GWT team and they'll eventually absorb or re-work anything we do on that front.

FYI, NavigableMap/NavigableSet are coming: http://gwt-code-reviews.appspot.com/1839803/
Will be in GWT 2.6 (2.5 is in RC, no ETA yet for 2.6, as it'll be the first release driven by the new Steering Committee)

Christian Gruber

unread,
Sep 26, 2012, 2:54:40 AM9/26/12
to Thomas Broyer, guava-...@googlegroups.com, Gregory Kick, Raymond Rishty
Yep.  Brian S. and I spoke briefly today and he mentioned that.  -cg.

Louis Wasserman

unread,
Sep 26, 2012, 12:45:05 PM9/26/12
to Thomas Broyer, guava-...@googlegroups.com, Gregory Kick, Raymond Rishty
FYI, NavigableMap/NavigableSet are coming: http://gwt-code-reviews.appspot.com/1839803/
Will be in GWT 2.6 (2.5 is in RC, no ETA yet for 2.6, as it'll be the first release driven by the new Steering Committee)
I know, since I'm the one who's submitting that code to GWT ;)

Louis

Christian Gruber

unread,
Sep 26, 2012, 1:30:17 PM9/26/12
to Louis Wasserman, Thomas Broyer, guava-...@googlegroups.com, Gregory Kick, Raymond Rishty
So Louis may want to write a more "announce" letter, but the 13.0 jdk5 backport is now in the maven repository.  Just use guava-jdk5 as your artifactId and off you go.  I'm off for a few days, but I thought I'd put that note out.  

Christian.
--

Louis Wasserman

unread,
Dec 21, 2012, 11:23:26 AM12/21/12
to Marcin Mikosik, Raymond Rishty, Thomas Broyer, Gregory Kick, guava-...@googlegroups.com

That would be because 14.0 has not been released, only a release candidate.  14.0 will have a back port when it is released.

On Dec 21, 2012 1:13 AM, "Marcin Mikosik" <marcin....@gmail.com> wrote:
Hi Christian,

Can you add link to that backported-version to guava-13-release-notes page please? (http://code.google.com/p/guava-libraries/wiki/Release13)
There's no place in whole guava documentation that would mention that such backport exists which makes it quite hard to find. 

Do you plan to make such backports for future guava releases? Can't find backport for version 14 anywhere.

marcin

sulema...@gmail.com

unread,
Jun 16, 2015, 9:03:53 AM6/16/15
to guava-...@googlegroups.com, g...@google.com, t.br...@gmail.com, marcin....@gmail.com, raymond...@gmail.com
can we use GWT 2.6.1 version with Java 5? or What's the maximum GWT version we can go with java 5? thanks.

Thomas Broyer

unread,
Jun 16, 2015, 10:12:18 AM6/16/15
to guava-...@googlegroups.com, sulema...@gmail.com, marcin....@gmail.com, t.br...@gmail.com, g...@google.com


On Tuesday, June 16, 2015 at 3:03:53 PM UTC+2, sulema...@gmail.com wrote:
can we use GWT 2.6.1 version with Java 5? or What's the maximum GWT version we can go with java 5? thanks.

I fail to see the relationship to Guava but anyway: according to https://github.com/gwtproject/gwt/commit/fa29596ebe9909f3cc1c671bb42a657b25903fac, 2.5.0 was the first version targeting Java 6; so the last one supporting Java 5 would be 2.4.0.
But Java 5 reached EOL ~5½ years ago already! http://www.oracle.com/technetwork/java/eol-135779.html (for public updates that is)
If you really need to use Java 5 on the server side (GWT-RPC), you could probably use some bytecode rewriter to make gwt-servlet.jar compatible with Java 5 (with a bit of luck, Retrolambda might work); and use a more recent version of Java for development (Retrolambda requires Java 8, FWIW).

Please follow-up to google-we...@googlegroups.com if you need to discuss further.
Reply all
Reply to author
Forward
0 new messages