-
Story
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
True
-
None
-
False
-
-
Motivation
Nowadays, Quarkus developers who create a new project in code.quarkus.redhat.com need to change the versions to productized OptaPlanner extensions.
Also we don't run tests together with Quarkus releases when there are CVEs / patches released etc.
Goal
Make Red Hat build of OptaPlanner part of Quarkus platform
Scenarios
As a developer, I need to create a new project in code.quarkus.redhat.com or use Quarkus CLI with productized versions of RHBOP so that I don't have to configure versions manually.
Expected outcomes
RHBOP will follow the build process in Quarkus platform: https://docs.google.com/document/d/1INiaJ2j80aUSHGTTihbmXxMCHsQXur7tDZykyp8HZvY/edit#heading=h.bgopievo7xk8
RHBOP quarkus extensions will be labeled supported in Quarkus catalog
RHBOP quarkus extensions will be productized in Quarkus catalog and developers will be able to use Quarkus CLI
- causes
-
RHBOP-38 Version misalignment of drools for RHBOP and Quarkus platform
- Verified
-
RHBOP-44 [QUARKUS PLATFORM]Unexpected files found in the maven-repo.zip
- Verified
-
RHBOP-46 [QUARKUS-PLATFORM]Unapproved jfreechart license used in maven-repo.zip
- Closed
-
QUARKUS-2899 depsToBuild report request to productize artefact for RHBOP that was already productized
- Closed
-
RHBOP-43 [QUARKUS-PLATFORM]Unexpected old artifact in maven-repo.zip
- Closed
-
RHBOP-45 [QUARKUS PLATFORM] Unavailable sources
- Closed
-
RHBOP-47 [QUARKUS PLATFORM]Upstream Transitive dependencies quarkus-awt, org-cracc in extensions
- Closed
- is related to
-
QUARKUS-2834 Include OptaPlanner in 2.13 product platform
- Closed
-
RHBOP-42 Remove javadoc references on upstream BOM
- Closed