Hey. Call to #java #developers here. Are you stuck on #Java8 projects?
Hey. Call to #java #developers here. Are you stuck on #Java8 projects?
#Streams in #Java have been available since #Java8 and are still receiving new features up to #Java24. In this first blog post in the series on streams, I'll start with streams, provide an overview, and show the first steps with gatherers...
https://svenruppert.com/2025/03/29/from-java-8-to-24-the-evolution-of-the-streams-api/
Google Blobstore Tutorial
https://happycoding.io/tutorials/google-cloud/java-8/blobstore
#tutorial #googlecloud #java8 #javascript #google #cloud #blobstore
Google Blobstore Tutorial
https://happycoding.io/tutorials/google-cloud/java-8/blobstore
#tutorial #googlecloud #java8 #javascript #google #cloud #blobstore
Google Authentication Tutorial
https://happycoding.io/tutorials/google-cloud/java-8/authentication
#tutorial #googlecloud #java8 #java #server #google #cloud #authentication
Now this is a puzzle, and all I need do is tell you it is #Tomcat9 on #Java8 running #Ubuntu 18.04 to set most of you running, but here's the thing: starting around midnight on the 18th, tomcat will no longer run. There's been no changes other than automated software updates.
catalina.sh start shows the webapps loading, no worries, no alarms, gets to the last one and reports "Killed." and sure enough, it is. Not a shred of log evidence, no kernel messages (ie OOM), nothing that I can detect.
Google Cloud Setup (Java 8)
Why is this compiling in Java?
BiConsumer<List<String>, String> test = List::add;
In eclipse or IntelliJ on inspection List::add points to List.add(E e) returning Boolean primitive, which is not a BiConsumer. A single argument.
What is happening here, there is some other method or some compiler magic?
Or add method is effectively equivalent to add(List<String> this, String arg), strange syntax not normally used but compiles, note first arg name has to be this.
It sounds pretty interesting if I would be able to easily migrate my older #opensource #Java8 projects to #Java17.
However, I still need to answer some of my core questions
- Is there any impact if you are not using #AWS?
- How will this tool cope with the current dependency to the #RTP portion of JMF (yep, the old buggy Java Media Framework)?
Upgrade your Java applications with Amazon Q Code Transformation (preview) | AWS News Blog
https://aws.amazon.com/blogs/aws/upgrade-your-java-applications-with-amazon-q-code-transformation-preview/
I am working in a team on upgrading a large #Java8 UI application to #Java17, and I really like the way #Git helps the collaboration.
For discovery, we started an experimental branch and flipped the switch to Java 17 in the build process. Nearly everything from specific Gradle plugins needing to be updated, XML-DSIG SHA1 being disabled by secure mode, SimpleDateFormatter default formatting pattern change starts to show first during build, then through the unit, integration and UI tests...
While tinkering with a totally unrelated stuff yesterday, I stumbled over `Chronology` API in #Java and realised that there's a `HijrahChronology` implementation to handle Islamic calendar with full support for localization. And it has been available since #Java8 !
https://www.naiyerasif.com/post/2023/08/05/islamic-calendar-in-java/