FWIW we've been using Java 8 on all our servers and development machines since its release. No problems. Also, lambdas, streams and default methods rock :).
Considering The Legacy Burden That Must Not Be Mentioned the ride to JDK 9 might be a little rockier though… http://blog.codefx.org/java/dev/how-java-9-and-project-jigsaw-may-break-your-code/ - hugi > On 30. apr. 2015, at 18:13, Chuck Hill <[email protected]> wrote: > > He was just indicating that it was an appropriate time for Wonder to be > updated for Java 7! :-P > > > On 2015-04-30, 11:11 AM, "Ken Anderson" wrote: > > and your point is? :) We live in EOL land! > >> On Apr 30, 2015, at 2:10 PM, Ramsey Gurley <[email protected] >> <mailto:[email protected]>> wrote: >> >> Java 7 appears to be EOL starting tomorrow >> >> https://www.java.com/en/download/faq/java_7.xml >> <https://www.java.com/en/download/faq/java_7.xml> >> >> >> On Apr 29, 2015, at 7:44 AM, David Avendasora <[email protected] >> <mailto:[email protected]>> wrote: >> >>> Hey all >>> >>> About a year ago a bunch of work to make Wonder Java 7 compatible. But the >>> branch is now 86 commits behind the master branch (Wonder 6). >>> >>> I propose we: >>> 1) Create a branch at the current head of master called Wonder_6 for >>> 6-specific bug fixes going forward >>> 2) Merge Wonder_7 branch into Master and then delete it. >>> 3) Create the *first* release of Wonder 7 from Master >>> 4) Work through as much of the current pull requests as possible, making >>> sure they work well with Java 7, create a final Wonder_7 release >>> 3) Create Wonder_7 branch for 7-specific bug fixes going forward >>> 5) Use Master for ongoing modern java development until we transition to >>> Wonder_9 >>> >>> If there are features that are added to the more modern branches but you >>> can’t use them because you are limited to Java 6 or 7, then you will be >>> allowed to create pull requests to bring those commits to older branches >>> the the work to do so would be on the developer wanting the back-porting. >>> Not on the original developer. >>> >>> What does everyone say? >>> >>> Dave >>> >>> ————————————————————————————— >>> WebObjects - so easy that even Dave Avendasora can do it!™ >>> ————————————————————————————— >>> David Avendasora >>> Senior Software Abuser >>> Nekesto, Inc. >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Webobjects-dev mailing list ([email protected] >>> <mailto:[email protected]>) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com >>> >>> <https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com> >>> >>> This email sent to [email protected] <mailto:[email protected]> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list ([email protected] >> <mailto:[email protected]>) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/kenlists%40anderhome.com >> >> <https://lists.apple.com/mailman/options/webobjects-dev/kenlists%40anderhome.com> >> >> This email sent to [email protected] <mailto:[email protected]> > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/hugi%40karlmenn.is > > This email sent to [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
