Details
-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
7.11.1.GA
-
None
-
False
-
False
-
Undefined
-
1. Download and put global maven settings.xml
file to use private repo in ~/.m2/
2a. Go to https://code.quarkus.redhat.com/?extension-search=OptaPlanner
3a. Choose OptaPlanner core and download project
or
2b. Run mvn io.quarkus:quarkus-maven-plugin:1.11.6.Final-redhat-00001:create -DprojectGroupId=com.example -DprojectArtifactId=optaplanner-quickstart -Dextensions="resteasy,resteasy-jackson,optaplanner-quarkus,optaplanner-quarkus-jackson" -DplatformGroupId=com.redhat.quarkus -DplatformVersion=1.11.6.Final.redhat-00001 -DnoExamplesExpected to see in build logs OptaPlanner 8.5.0.Final-redhat-x
1. Download and put global maven settings.xml file to use private repo in ~/.m2/ 2a. Go to https://code.quarkus.redhat.com/?extension-search=OptaPlanner 3a. Choose OptaPlanner core and download project or 2b. Run mvn io.quarkus:quarkus-maven-plugin:1.11.6.Final-redhat-00001:create -DprojectGroupId=com.example -DprojectArtifactId=optaplanner-quickstart -Dextensions="resteasy,resteasy-jackson,optaplanner-quarkus,optaplanner-quarkus-jackson" -DplatformGroupId=com.redhat.quarkus -DplatformVersion=1.11.6.Final.redhat-00001 -DnoExamples Expected to see in build logs OptaPlanner 8.5.0.Final-redhat-x
Description
Currently we have in product release for Quarkus 1.11.6.Final-redhat-00001 the following dependency that uses community build of OptaPlanner 8.1.0.Final instead of OptaPlanner 8.5.0.Final-redhat
That is happens because of the release workflow we currently have
So quarkus-universe-bom provided after Quarkus 1.11.6.Final-redhat-0001 GA should be updated to be able to handle productized OptaPlanner dependency after OptaPlanner 8.5.0.Final-redhat-0002 GA release.
