Hello everyone, I'm super pleased to be able to share that thanks to another great contribution by Petri (right after FINERACT-730, you're On A Roll!), we have just been able to merge https://github.com/apache/fineract/pull/820. This switches Fineract (non-CN) from Java 8 to Java 11 (only), on the develop branch, and resolves https://issues.apache.org/jira/browse/FINERACT-846.
You must now all use Java 11 instead of 8 for local development. -- Personally I recommend using OpenJDK for local development, which is simple to install through your favourite package manager if you use a real ;) operating system, or downloaded e.g. from https://adoptopenjdk.net. Other Java 11 work as well, of course. (For your production environments, I personally would recommend using a supported JDK distribution, if you're serious, but that's another discussion.) Running e.g. "./gradlew bootRun" on Java 8 instead of Java 11 will now fail with "Execution failed for task ':compileJava'. > Could not target platform: 'Java SE 11' using tool chain: 'JDK 8 (1.8)'." <== This will help people searching for this find this announcement in the future... ;-) At runtime, this makes it possible to use a modern modern a recent JVM (which was technically hypothetically already possible with a Java 8 based WAR, but typically isn't done). At development time, this work unlocks a number of next steps, such as using Java 11 language syntax in all of Fineract's source code, and depending on modern libraries requiring Java 11. We look forward to Pull Requests from all of you! Please join me in thanking Petri for his 2nd major contribution. Hats off for having figured out that pesky SSL issue... ;-) Now let's all toast to Fineract's future developments using Java 11! Best, M. _______________________ Michael Vorburger http://www.vorburger.ch On Mon, Nov 25, 2019 at 8:43 AM Michael Vorburger <[email protected]> wrote: > Hello, > > The upgrade to more recent Spring versions just got merged (today) into > the develop branch; Ivan did this (thanks again), so contributions for that > are no longer needed. We do, of course, welcome any contributions with > upgrades for other dependencies. > > The upgrade to Java 11 is something I looked into in > https://github.com/apache/fineract/pull/609; it's not quite working yet. > Would you perhaps like to help with that? > > Best, > M. > _______________________ > Michael Vorburger > http://www.vorburger.ch > > > On Sun, Nov 10, 2019 at 7:33 AM Aleksandar Vidakovic < > [email protected]> wrote: > >> Hi Ram, >> >> ... we are currently testing a completely upgraded Fineract 1.x (Spring >> 5.2.0.RELEASE, Spring Boot 2.2.1.RELEASE, Jersey 2.29, and pretty much >> every other dependency upgraded) that is running on OpenJDK 12 (I'm pretty >> sure it will run the same way on 11 and 13). Goal is to offer this as a >> pull request soon. >> >> This upgrade is intended to be a drop in replacement (i. e. can be used >> with Community app, same REST endpoints, runs most - 93% - of the >> integration tests successfully); some minor work is left to do. >> >> Just FYI >> >> On Sun, Nov 10, 2019 at 3:19 AM Rama Reddy <[email protected]> >> wrote: >> >>> >>> Hi, >>> Just would like check if anybody started work on migrating java version >>> to 11 for fineract 1.x. >>> Would be great if you can share your experience with w.r.t >>> - impact analysis >>> - amount of work involved.. >>> - if any feature branch in place? >>> >>> Thanks >>> Ram >>> Sent from Yahoo Mail on Android >>> <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature> >>> >>
