Uploaded image for project: 'Maven Resolver'
  1. Maven Resolver
  2. MRESOLVER-357

ConflictResolver STANDARD verbosity misbehaves

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 1.9.8, 1.9.9
    • 1.9.10
    • Resolver
    • None

    Description

      As per user report, the 1.9.8 and 1.9.9 versions produce different "verbose tree" than previous versions:

      Input node:
      some-group:a:jar:1.0 [compile]
      +- some-group:b:jar:1.0 [compile]
      |  +- some-group:c:jar:1.0 [compile]
      |  +- some-group:c:jar:2.0 [compile]
      |  \- some-group:d:jar:1.0 [compile]
      +- some-group:c:jar:2.0 [compile]
      +- some-group:c:jar:1.0 [compile]
      \- some-group:d:jar:2.0 [compile]
      
      Transformed node:
      some-group:a:jar:1.0 [compile]
      +- some-group:b:jar:1.0 [compile]
      |  \- some-group:c:jar:2.0 [compile] (nearer exists)
      +- some-group:c:jar:2.0 [compile]
      \- some-group:d:jar:2.0 [compile] 

      The some-group:d:jar:1.0 [compile] should not be removed.

      Seems that code comment "leaving only 1 loser" is present in comments only, but the actual code does not deliver this promise.

      In fact, the check is wrong: it should check for same GA child count and not ANY child count.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: