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

Identify dependencies within a dependencyManagement block

    XMLWordPrintable

Details

    • Story
    • Resolution: Unresolved
    • Major
    • None
    • 5.1.3.Final
    • None
    • None
    • False
    • 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:_+
    • Undefined
    • ---
    • ---
    • Priority Backlog

    Description

      Dependencies within a dependencyManagement block are not identified by WINDUP.
      So for example the dependency on Quarkus declared here would not be picked up.

      Were as the other dependencies defined outside of a dependencyManagement block (example) will.

      The DiscoverMavenProjectsRuleProvider.java is the class that limits the discovery of dependencies to those declared in the path /project/dependencies/dependency.

      WINDUP also needs also cater for this path to dependencies
      project/dependencyManagement/dependencies/dependency

      Attachments

        Activity

          People

            Unassigned Unassigned
            pcattana Philip Cattanach
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: