CDV ❯ Improve error message when Resolver is unable to locate a bundle dependency.

• Type: New Feature
• Status: Closed
• Priority: 2 Major
• Resolution: Fixed
• Component/s:
• Labels:

• Assignee: hhuynh
• Reporter: juris
• Created: April 03, 2008
• Votes: 0
• Watchers: 0
• Updated:

  May 12, 2008
• Resolved:

  April 24, 2008

Description

Improve error message when Resolver is unable to locate a bundle dependency.

We need to improve the error message for when a bundle dependency is not found. Currently we only list the name of the unresolved bundle, but we do not indicate why we were looking for that bundle. It would help a lot in diagnosing these type of problem if we could at least show the trail of how we ended up looking for a certain bundle by listing the stack of bumdles that led the resolver to look for the problematic/unresolved bundle.

Eg:

Unable to resolve bundle ‘foobar-1.0.0’, this is required by bundle ‘foozoo-1.0.1’, which is required by ‘fooquux-2.0.0’, etc…

(or something like a stacktrace)

Comments

Juris Galang 2008-04-18

Fixed in trunk, see revs:

• 8261
• 8284
• 8294
• 8295
• 8304

Merged in 2.6 as revs:

• 8328
• 8329
• 8330

Fiona OShea 2008-04-25

Changed Target to Pacheco as this was fixed early.