-
Notifications
You must be signed in to change notification settings - Fork 448
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
Quickstarts : Update Micronaut version in quickstarts/gradle/micronaut
#2774
Comments
Hello @rohanKanojia, can I work on this issue? |
I would like to work on this, can you assign this to me? |
Hi @manusa , Can you help me with this issue, unable to build micronaut-customized-image: Downloaded from central: https://repo.maven.apache.org/maven2/com/marcnuri/helm-java/linux-amd64/0.0.6/linux-amd64-0.0.6.jar (24 MB at 7.1 MB/s) |
Component
None
Task description
Description
This is a follow-up to #2753
Our Micronaut Gradle quickstarts are using an outdated version of Micronaut framework:
https://github.com/eclipse/jkube/blob/b64915ec6090dcb0171e45b6372052278210e6f3/quickstarts/gradle/micronaut-customized-image/gradle.properties#L15
https://github.com/eclipse/jkube/blob/b64915ec6090dcb0171e45b6372052278210e6f3/quickstarts/gradle/micronaut/gradle.properties#L15
Micronaut 4 now requires Java 17 as baseline. Maybe we should not update this quickstart directly to 4.x. For now, updating it to the latest 3.x version (
3.9.7
at the time of creating this issue) would be okay.After updating Micronaut version, you should verify that quickstart is building fine and is also working as specified in their respective README . You can take a look at this YouTube video Sprint 192 - Eclipse JKube Micronaut integration to see how to try it out.
Expected Behavior
Micronaut Quickstart is updated to latest
3.x
versionAcceptance Criteria
3.x
versionBefore you start 🔴
👇 👇 👇 👇 👇 👇 👇 👇 👇 👇👇👇👇👇👇👇
Make sure you read the contributing guide first. Pay special attention to the ECA agreement section and the requirement to sign-off your commit.
How to manually test my changes
Kubernetes
If you don't have a real Kubernetes cluster available (most probably), you can use Minikube or Kind to test with a local cluster.
OpenShift
If you don't have a real OpenShift cluster available (most probably), you can use Red Hat's developer Sandbox for Red Hat OpenShift. The only requirement is to have a Red Hat account.
Once you have your Sandbox environment, you'll need to download the oc tool from the cluster console.
(Press the
?
icon and from the context menu selectCommand line tools
, you'll be redirected to https://$subdomain.openshiftapps.com/command-lines-tools where you'll be able to download the CLI for your platform)The text was updated successfully, but these errors were encountered: