Camunda Engine Quarkus Extension

XMLWordPrintable

    • Type: Feature Request
    • Resolution: Done
    • Priority: L3 - Default
    • 7.16.0, 7.16.0-alpha5
    • Affects Version/s: None
    • Component/s: quarkus
    • None

      User Story

      As a user, I can add the Camunda Engine Quarkus Extension to my Application to use a single-embedded Process Engine.

        1.
        		 [DOCS] Persistence integration Sub-task Closed Tassilo Weidner-Mühl
        2.
        		 Engine CDI module is integrated into Quarkus Extension Sub-task Closed Tassilo Weidner-Mühl
        3.
        		 Increase surefire heap space for tests Sub-task Closed Tassilo Weidner-Mühl
        4.
        		 Bump Quarkus to 2.1.2.Final Sub-task Closed Tassilo Weidner-Mühl
        5.
        		 [DOCS] I can read documentation on Quarkus resource deployment Sub-task Closed Nikola Koevski
        6.
        		 Fix failing history level stages Sub-task Closed Tassilo Weidner-Mühl
        7.
        		 [OPTIONAL] H2 in-memory database is configured by default Sub-task Closed Tassilo Weidner-Mühl
        8.
        		 Bump Quarkus to 2.1.0.Final Sub-task Closed Tassilo Weidner-Mühl
        9.
        		 CDI: Investigate impact of missing Extension API support Sub-task Closed Tassilo Weidner-Mühl
        10.
        		 Add README.md files Sub-task Closed Nikola Koevski
        11.
        		 [OPTIONAL] In Quarkus Extension, engine can be configured via application.properties file Sub-task Closed Nikola Koevski
        12.
        		 Engine can be bootstrapped Sub-task Closed Nikola Koevski
        13.
        		 CDI: Investigate behavior of @Alternative annotation in conjunction with @Priority(1) Sub-task Closed Tassilo Weidner-Mühl
        14.
        		 Change default history level to full Sub-task Closed Tassilo Weidner-Mühl
        15.
        		 I can deploy modelling resources Sub-task Closed Nikola Koevski
        16.
        		 Dev mode is broken Sub-task Closed Tassilo Weidner-Mühl
        17.
        		 Build of Quarkus Extension fails with Maven 3.2.5 Sub-task Closed Tassilo Weidner-Mühl
        18.
        		 Add extension to BOM Sub-task Closed Tassilo Weidner-Mühl
        19.
        		 [DOCS] I can read documentation on configuring the Quarkus extension Sub-task Closed Nikola Koevski
        20.
        		 Create simple example for the alpha4 release Sub-task Closed Tassilo Weidner-Mühl
        21.
        		 Register strong UUID generator Sub-task Closed Tassilo Weidner-Mühl
        22.
        		 UPGRADE-databases-from-714-h2 stage fails Sub-task Closed Tassilo Weidner-Mühl
        23.
        		 CDI: Investigate if process engine should be replaceable Sub-task Closed Tassilo Weidner-Mühl
        24.
        		 CDI: Investigate impact of missing support of Passivation and passivating scopes Sub-task Closed Tassilo Weidner-Mühl
        25.
        		 CDI: Rewrite currently failing tests Sub-task Closed Tassilo Weidner-Mühl
        26.
        		 New engine CDI tests are detected by the Quarkus extension module Sub-task Closed Tassilo Weidner-Mühl
        27.
        		 CDI: Investigate fix for missing BeanManager#getELResolver support Sub-task Closed Tassilo Weidner-Mühl
        28.
        		 CDI: Investigate if interceptors should be enabled by default Sub-task Closed Tassilo Weidner-Mühl
        29.
        		 Job Executor is functional Sub-task Closed Nikola Koevski
        30.
        		 CDI: Register @BusinessProcessScoped scope Sub-task Closed Tassilo Weidner-Mühl
        31.
        		 CDI: Investigate memory leak log for @Dependent scoped beans Sub-task Closed Tassilo Weidner-Mühl
        32.
        		 Investigate Quarkus 2.0 impact on Quarkus support Sub-task Closed Nikola Koevski
        33.
        		 The Quarkus JobExecutor uses its own thread pool Sub-task Closed Nikola Koevski
        34.
        		 Persistence via Quarkus Agroal Sub-task Closed Tassilo Weidner-Mühl
        35.
        		 [EXAMPLE] Datasource example Sub-task Closed Nikola Koevski
        36.
        		 In Webapps, update powermock & mockito to work with JDK 9+ Sub-task Closed Tassilo Weidner-Mühl
        37.
        		 [EXAMPLE] Process Engine Plugin Spin example Sub-task Closed Tassilo Weidner-Mühl
        38.
        		 CDI: Investigate and decide if beans.xml needs a replacement Sub-task Closed Tassilo Weidner-Mühl
        39.
        		 CI Pipelines execute Quarkus stages Sub-task Closed Tassilo Weidner-Mühl
        40.
        		 Quarkus Extension is compiled with Java 11 to Java 8 compatible bytecode Sub-task Closed Unassigned
        41.
        		 Engine CDI module tests are run against Quarkus environment Sub-task Closed Tassilo Weidner-Mühl
        42.
        		 Engine can be configured programmatically Sub-task Closed Nikola Koevski
        43.
        		 CDI: Investigate the default configuration of auto-inject-fields Sub-task Closed Tassilo Weidner-Mühl
        44.
        		 I can read documentation Sub-task Closed Tassilo Weidner-Mühl
        45.
        		 CDI: Make marking DefaultContextAssociationManager$RequestScopedAssociation bean as unremovable more robust Sub-task Closed Tassilo Weidner-Mühl
        46.
        		 Examples exist Sub-task Closed Unassigned
        47.
        		 [DOCS] I can read documentation about the CDI integration Sub-task Closed Tassilo Weidner-Mühl
        48.
        		 [DOCS] I can read documentation on Quarkus version support and supported deployment scenarios Sub-task Closed Nikola Koevski

            Assignee:
            Hariharan Parasuraman
            Reporter:
            Daniel Meyer
            Tassilo Weidner-Mühl Tassilo Weidner-Mühl
            Nikola Koevski Nikola Koevski
            Hariharan Parasuraman Hariharan Parasuraman
            Votes:
            8 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: