Update Maven Java stack

[azatsarynnyy]

What does this PR do?:

Summarize the changes. Are any stacks or samples added or updated?

• update schema to 2.2.2;
• use https protocol for the java-maven devfile

Which issue(s) this PR fixes:

Link to github issue(s)
eclipse-che/che#22869

PR acceptance criteria:

• Contributing guide
  Have you read the devfile registry contributing guide and followed its instructions?
• Test automation
  Does this repository's tests pass with your changes?
• Documentation
  Does any documentation need to be updated with your changes?
• Check Tools Provider
  Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)

How to test changes / Special notes to the reviewer:

https://workspaces.openshift.com/#https://raw.githubusercontent.com/azatsarynnyy/registry/java-maven-update/stacks/java-maven/1.3.1/devfile.yaml

[openshift-ci]

Hi @azatsarynnyy. Thanks for your PR.

I'm waiting for a devfile member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[azatsarynnyy]

also, I opened odo-devfiles/springboot-ex#5

[Jdubrick]

/ok-to-test

[Jdubrick]

Bumping from 1.3.0 to 1.3.1 to contain schema change + http -> https is identical to what was done here for example:
go 1.2.0 -> go 1.2.1

Since it was done before for consistency I'm okay with this change but I do wonder if using a patch version for increasing the schema version is the right move instead of creating a new 1.4.0 stack?

cc @michael-valdron @thepetk

[svor]

lgtm

[thepetk]

in general lgtm now that we have bumped the devfile version.

@kadel as the owner of the stack could you please review the PR?

[ibuziuk]

@thepetk can we merge ?

[thepetk]

@thepetk can we merge ?

@ibuziuk I've pinged the owner directly. Once is approved by the stack owner I'll merge it :)

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: azatsarynnyy, ibuziuk, kadel, svor
Once this PR has been reviewed and has the lgtm label, please assign thepetk for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment