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

Detect Artifacts referenced within the plugins section of the pom.xml file

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • MTA CLI
    • None
    • False
    • Hide

      None

      Show
      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 218, AMM Sprint 219
    • None

      The <project> construct can be used to identify artifacts declared as dependencies.
      It should also be possible to identify artifacts declared within other elements of the pom.xml file, for example the plugins section of the pom. The example below is extracted from this example pom.xml

      <build>
      <plugins>
      <plugin>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-maven-plugin</artifactId>
      </plugin>
      </plugins>
      </build>

      It should also be possibel to identify dependencies declared within the dependencies-management tag.

              jleflete@redhat.com Juanma Leflet Estrada
              pcattana Philip Cattanach
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: