Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-3702

Project kogito-quarkus-dm-archetype contains hardcoded quarkus version in plugin configuration

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.11.0.GA
    • 7.11.0.GA
    • Build and Assembly
    • None
    • False
    • False
    • Release Notes
    • CR1
    • CR2
    • Undefined
    • Hide

      After the project is generated, change manually quarkus-maven-plugin version to reference the existing property using 

      ${quarkus.version}

      .

      Show
      After the project is generated, change manually quarkus-maven-plugin version to reference the existing property using ${quarkus.version} .

    Description

      When generating project using archetype in subject, there's following configuration of quarkus-maven-plugin:

           <plugin>
        <groupId>io.quarkus</groupId>
        <artifactId>quarkus-maven-plugin</artifactId>
        <version>1.11.4.Final</version>
        <executions>
          <execution>
            <goals>
              <goal>build</goal>
              <goal>generate-code</goal>
              <goal>generate-code-tests</goal>
            </goals>
          </execution>
        </executions>
      </plugin>

      While instead of the explicit value for plugin version there should be reused property 

      <quarkus.version>1.11.4.Final</quarkus.version>

      .

      This can potentially cause troubles when users are overriding kogito version either in properties section or by passing env property.

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-5140 Quarkus archetype - defer expansion of properties with versions

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              ant@redhat.com Ant Stephenson
              jstastny@redhat.com Jan Stastny
              Jan Stastny Jan Stastny
              Jan Stastny Jan Stastny
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: