Skip to content
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

Fix date typo #18

Merged
merged 3 commits into from
Jan 1, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -3,11 +3,11 @@ draft: false
title: "Quick Upgrade Trick for App Engine Java 11/17"
author: Joe Lust
layout: post
date: 2024-07-01
date: 2024-10-01
featured_image: /img/gcf_next_gen.jpeg
image: /img/java-17-upgrade.webp
url: /2024/0/01/quick-upgrade-app-engine-java-11-17/
summary: "Quickly modernize your App Engine Java 8 codebase to run on Java 11 & 17!"
url: /2024/10/01/quick-upgrade-app-engine-java-17/
summary: "Quickly modernize your App Engine Java 8 codebase to run on Java 17!"
tags:
- app-engine
- app-engine-flex
Expand All @@ -21,7 +21,7 @@ tags:
- java-17
---

Java modernization is sweeping over Google Cloud App Engine 🎉. While Java 8 support dates back to [circa 2015][0], after many [+1 votes][1] the feature was delivered to App Engine Flex [in 2022][2]. Now however comes the deprecation reckoning. Java 8 must go.
Java modernization is sweeping over Google Cloud App Engine 🎉. While Java 8 support dates back to [circa 2015][0], after many [+1 votes][1] the feature was delivered to App Engine Flex [in 2022][2]. Now however comes the deprecation reckoning. Java 8 must go, as well as Java 11 shortly thereafter.

If you've seen this error message, this article is for you:

Expand Down