-
Story
-
Resolution: Done
-
Critical
-
None
-
None
Docs:
Camel Quarkus ENG Component Planning Document
- document maps the progress of porting the Camel 3 components, dataformats, languages, EIP (TBD), others into Camel Quarkus runtime - JVM and Native mode
Definition of done:
- identify and fill the high-level features/use cases (even the ones it brings via transitive dependency on Camel 3 or Quarkus)
- identify transitive dependencies on quarkus extensions and make sure it is supported on upcoming Quarkus release
- identify if the use cases/features are present in quickstarts/camel-quarkus-examples
- identify the test coverage of the high-level features in integration-test or the quickstarts
- PM/ENG/QE agree on if everything of the features is supported in the product
- review if the tests contains test for each high level feature of the component
- is related to
-
ENTESB-16540 Add coverage for more HAPI versions in HL7
- Closed
-
ENTESB-16703 Add ability to test HL7 extension with multiple HAPI implementations
- Closed
- relates to
-
CEQ-2170 HL7 support in Camel Quarkus
- Closed