Details
-
Task
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
CP: sprint 92, CP: sprint 94, CP: sprint 95, CP: sprint 96, CP: sprint 97, CP: sprint 98, CP: sprint 99, CP: sprint 100, CP: sprint 101, CP: sprint 102, CP: sprint 103, CP: sprint 105
-
8
-
Core: Platform
-
R1 2021
Description
domain-model-runtime ships with the complete domain-models-interface-extensions submodule that contains the GenerateRunner class to generate Java files from RAML files.
We need this at compile time only.
The clean solution is a maven plugin, for example rmb-maven-plugin, that runs at compile time, and will not be included into the runtime artifact.
The RAML generating code is based on a library that uses Guava 19 that has a security vulnerability (RMB-283) and the library breaks for fixed Guava versions.
By moving the generating code into a maven plugin that runs a compile time only we can avoid to ship the runtime with vulnerable Guava.
TestRail: Results
Attachments
Issue Links
- blocks
-
MODEUS-86 Guava security vulnerability CVE-2018-10237
-
- Closed
-
-
MODEUSHARV-11 Guava security vulnerability CVE-2018-10237
-
- Closed
-
-
MODLOGSAML-76 Upgrade to RMB 31.x and JDK 11
-
- Closed
-
-
MODLOGSAML-86 Upgrade mod-login-saml to RMB v33 (and JDK11)
-
- Closed
-
-
RMB-283 com.google.guava 19.0 security vulnerabilities (CVE-2018-10237)
-
- Closed
-
-
RMB-571 Remove com.google Guava runtime dependency
-
- Closed
-
- duplicates
-
RMB-233 Avoid bundling GenerateRunner
-
- Closed
-
- is cloned by
-
RMB-785 Implementation/Testing/Code Review: Convert GenerateRunner into maven plugin
-
- Closed
-
- relates to
-
RMB-328 Make RMB OpenJDK 11 compliant
-
- Closed
-
-
RMB-852 Update documentation for domain-models-interface-extensions removal
-
- Closed
-