Uploaded image for project: 'WINDUP - Red Hat Application Migration Toolkit'
  1. WINDUP - Red Hat Application Migration Toolkit
  2. WINDUP-3415

Windup CLI - 'artifactId' should be a constant

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • 5.3.0.Final
    • MTR Build Pipeline
    • None
    • False
    • None
    • False
    • Hide
      * *Why we missed the bug?*
       ** Pick to proper answer from drop-down field upper.
       +_Additional comments:_+


       * *What is required:*
       ** Pick to proper answer from drop-down field upper.
       +_Additional comments:_+
      Show
      * *Why we missed the bug?*  ** Pick to proper answer from drop-down field upper.  +_Additional comments:_+  * *What is required:*  ** Pick to proper answer from drop-down field upper.  +_Additional comments:_+
    • ---
    • ---
    • AMM Sprint 220
    • None

      When building the CLI in the windup-distribution project, this message appears:

      [WARNING] 
      [WARNING] Some problems were encountered while building the effective model for org.jboss.windup:mta-cli:pom:5.3.1-SNAPSHOT
      [WARNING] 'artifactId' contains an expression but should be a constant. @ org.jboss.windup:${product-name}-cli:5.3.1-SNAPSHOT, /home/mrizzi/git/forked/windup-distribution/pom.xml, line 17, column 17
      [WARNING] 
      [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
      [WARNING] 
      [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
      [WARNING] 
      

      As reported, the pom has an artifactId dynamic value which is not supposed to be supported and hence to be fixed to avoid problems any time in the future like not being able to build the CLI anymore.

              mrizzi@redhat.com Marco Rizzi
              mrizzi@redhat.com Marco Rizzi
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: