-
Notifications
You must be signed in to change notification settings - Fork 10.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to Java 6 #32
Comments
Original comment posted by estebistec on 2008-04-11 at 04:44 PM "will include both forms in our release" Just a clarification question: will you be tagging releases from both branches? This |
Original comment posted by cbiffle on 2008-08-20 at 03:45 AM The 20080818 snapshot JAR seems to contain Java 6 class files -- they fail on my Java 5 machines with |
Original comment posted by jared.l.levy on 2008-08-20 at 04:47 PM The 20080818 release was supposed to be Java 5, but my environment was incorrect when Owner: jared.l.levy |
Original comment posted by jared.l.levy on 2008-08-21 at 12:25 AM I replaced the 20080818 release, which was built with Java 6, with a 20080820 release |
Original comment posted by kevinb9n on 2009-01-06 at 06:11 PM Sadly, this will probably not happen for a long time, due to the increased importance |
Original comment posted by estebistec on 2009-01-07 at 02:20 AM I think that's fine. It was probably more important (in the near time-range at |
Original comment posted by jared.l.levy on 2009-04-08 at 01:07 AM (No comment entered for this change.) Owner: --- |
Original comment posted by kevinb9n on 2009-09-17 at 06:02 PM (No comment entered for this change.) Labels: |
Original comment posted by bolinfest on 2010-04-27 at 03:54 AM Would it be possible to create a Java-1.6-specific build target for those of us who |
Original comment posted by kevinb@google.com on 2010-04-27 at 02:09 PM Actually, all you should have to do is give it your java 6 installation location as if it's the java 5. Everything will |
Original comment posted by jherico72 on 2010-07-16 at 03:39 PM The POM needs to be updated to reflect the change. Patch attached. |
Original comment posted by kevinb@google.com on 2010-07-16 at 05:47 PM What change? The change to requiring java 6 (described in this issue) is on hold indefinitely. |
Original comment posted by kevinb@google.com on 2010-07-30 at 03:53 AM (No comment entered for this change.) Labels: - |
Original comment posted by kevinb@google.com on 2010-07-30 at 03:56 AM (No comment entered for this change.) Labels: - |
Original comment posted by kevinb@google.com on 2011-01-27 at 02:14 PM (No comment entered for this change.) Labels: - |
Original comment posted by sahendrickson on 2011-04-17 at 05:45 AM Given that the change to java 6 has occurred (see issue 364), I'm unclear as to whether 1.5 will be supported or not. This issue indicates it will be, and issue 364 says it won't be. It seems this issue should be closed as won't fix, or issue 364 should be marked as a duplicate of this issue in order to make them consistent. More importantly, given that the code currently requires 1.6, the patch in comment #11 should be applied so that a Maven checkout and compile of the trunk is successful. A later branch (which only requires 1.5) could use the unpatched Maven configuration files that are currently in the trunk. But, without the patch, the Maven configuration is broken. See also issue 607 regarding the Maven configuration files. |
Original comment posted by cgdecker on 2011-04-17 at 03:01 PM Issue 364 just says that Guava requires 1.6 to compile. It doesn't say anything about requiring 1.6 to run... it's still targeted at 1.5. |
Original comment posted by kevinb@google.com on 2011-07-13 at 06:18 PM (No comment entered for this change.) Status: |
Original comment posted by kevinb@google.com on 2011-07-16 at 08:37 PM (No comment entered for this change.) Status: |
Original comment posted by kevinb@google.com on 2011-07-19 at 12:17 AM If we did this, would we have any volunteers to maintain the backport branch? |
Original comment posted by kevinb@google.com on 2011-07-19 at 12:18 AM (No comment entered for this change.) Blocking: #664 |
Original comment posted by raymond.rishty on 2011-07-19 at 11:14 AM I have some projects that are woefully stuck on Java 5, so I selfishly would like that to remain the target. OTOH it sounds like Guava could be improved by moving to 6, so I'd be willing to be that guy. |
Original comment posted by fry@google.com on 2011-12-10 at 03:13 PM (No comment entered for this change.) Labels: |
Original comment posted by wasserman.louis on 2011-12-21 at 01:30 PM I am willing to take on the Sorted->Navigable part of the migration, that being "my thing." |
Original comment posted by wasserman.louis on 2011-12-31 at 05:17 PM (No comment entered for this change.) Blocking: #51 |
Original comment posted by wasserman.louis on 2012-01-05 at 06:37 PM Any idea how we'll deal with GWT compatibility in the future? |
Original comment posted by kevinb@google.com on 2012-03-02 at 06:51 PM (No comment entered for this change.) Labels: |
Original comment posted by fry@google.com on 2012-03-05 at 07:23 PM (No comment entered for this change.) Status: |
Original comment posted by wasserman.louis on 2012-03-05 at 07:26 PM Woooooooooooooooooooo! |
Original comment posted by a.korzhevskiy on 2012-03-05 at 09:01 PM Indeed, it would be great to have Navigable* in GWT too |
Original comment posted by wasserman.louis on 2012-03-05 at 09:27 PM That may be a GWT issue, not a Guava issue...? |
Original comment posted by cpovirk@google.com on 2012-03-28 at 07:41 PM RE: comment 30, here's a dump of a related internal bug ("Consider making NavigableSet methods available in GWT ImmutableSortedSet"): """
Or we could stop manually emulating the GWT classes altogether. ... Very important thing that I forget: We can't easily test the new methods (i.e., test them with our collection-suite builders) unless they legitimately implement NavigableSet. That alone makes me favor that approach -- if we do this at all, which it's not clear that we should. ... Louis would also like to use this for SortedMultiset so that we don't propagate the SortedSet/NavigableSet distinction into the Multiset hierarchy: #942 |
Original comment posted by wasserman.louis on 2012-04-17 at 10:33 PM (No comment entered for this change.) Blocking: -#51 |
Original issue created by kevinb9n on 2007-11-01 at 08:12 PM
We will upgrade to requiring Java 6, but will create a Java 5-compatible
branch and will include both forms in our release.
Based on the changes listed in
http://java.sun.com/javase/6/docs/technotes/guides/collections/changes6.html
we'll have some work to do...
API -
Impl -
custom code wherever possible
probably other stuff I'm not thinking of.
The text was updated successfully, but these errors were encountered: