Update default version for java-wildfly-bootable-jar stack; set https protocol

[olexii4]

What does this PR do?:

Updates java-wildfly-bootable-jar stack:

Add new version 1.3.0

• Set HTTPS protocol for the endpoint
• Set the 1.3.0 version as the default one

Which issue(s) this PR fixes:

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:

[openshift-ci]

Hi @olexii4. 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/test-infra repository.

[thepetk]

I'd suggest bumping up to 1.3.0 instead of 1.2.1 because the schemaVersion goes from 2.1.0 to 2.2.2.

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

Another comment is if we would like to remove the version 1.2.0 completely (dir and stack.yaml record) like we did for #342

cc @michael-valdron @Jdubrick

[thepetk]

/ok-to-test

[olexii4]

@thepetk I have fixed the version.

[Jdubrick]

I'd suggest bumping up to 1.3.0 instead of 1.2.1 because the schemaVersion goes from 2.1.0 to 2.2.2.

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

Another comment is if we would like to remove the version 1.2.0 completely (dir and stack.yaml record) like we did for #342

cc @michael-valdron @Jdubrick

I think in this case we leave 1.2.0 because it is unchanged and we are adding 1.3.0 in addition, so people can choose to still reference 1.2.0 if they want by leaving it, wdyt?

Also @olexii4 you will need to sign your latest commit for DCO check to pass :)

[thepetk]

I'd suggest bumping up to 1.3.0 instead of 1.2.1 because the schemaVersion goes from 2.1.0 to 2.2.2.
@ehsavoie as you are the owner of the stack could you please review the PR?
Another comment is if we would like to remove the version 1.2.0 completely (dir and stack.yaml record) like we did for #342
cc @michael-valdron @Jdubrick

I think in this case we leave 1.2.0 because it is unchanged and we are adding 1.3.0 in addition, so people can choose to still reference 1.2.0 if they want by leaving it, wdyt?

Also @olexii4 you will need to sign your latest commit for DCO check to pass :)

Yeah I agree, that's why I had the doubt on this - cause the two versions have different schema versions. +1 on keeping the old version.

[olexii4]

I'd suggest bumping up to 1.3.0 instead of 1.2.1 because the schemaVersion goes from 2.1.0 to 2.2.2.
@ehsavoie as you are the owner of the stack could you please review the PR?
Another comment is if we would like to remove the version 1.2.0 completely (dir and stack.yaml record) like we did for #342
cc @michael-valdron @Jdubrick

I think in this case we leave 1.2.0 because it is unchanged and we are adding 1.3.0 in addition, so people can choose to still reference 1.2.0 if they want by leaving it, wdyt?

Also @olexii4 you will need to sign your latest commit for DCO check to pass :)

I have fixed it.

[thepetk]

/hold as we need the approval from the owner to merge the pr

[michael-valdron]

Another comment is if we would like to remove the version 1.2.0 completely (dir and stack.yaml record) like we did for #342

@thepetk #347 (comment)

[Jdubrick]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ehsavoie, Jdubrick, olexii4

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

The pull request process is described here

Needs approval from an approver in each of these files:

• stacks/OWNERS [Jdubrick]

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

[Jdubrick]

/unhold