Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-7854

Non directly managed imported and conflicting depMgt entries should warn

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 4.0.0-alpha-13, 4.0.0
    • POM
    • None

    Description

      The artificial (or "bolted on") scope "import" behaves wildly differently that rest of Maven, causes surprise to our users. For start, we should emit "actionable" warnings about these, ultimate goal is to align this behaviour with "maven way" of working ("closest occurence wins" vs current weird "direct occurrence then first occurence wins" strategy)

      See https://github.com/cstamas/MNG-7852 for reproducer.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MNG-8078 BOM POM import warnings are emitted on scopes and exclusions

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MNG-7906 Dependency Management import (BOM) does not work the "maven way"

          • Major - Major loss of function.
          • Open
          links to

          Web Link GitHub Pull Request #1211

          Web Link GitHub Pull Request #1370

          Activity

            People

              cstamas Tamas Cservenak
              cstamas Tamas Cservenak
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: