Closed Bug 658009 Opened 15 years ago Closed 15 years ago

Show warnings when a user tries to add a library with conflicting library names

Categories

(addons.mozilla.org Graveyard :: Add-on Builder, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED
Builder 0.9.6

People

(Reporter: smcarthur, Assigned: smcarthur)

Details

The SDK 1.0b5 now allows for modules of the same name in different libraries, so we no longer need to warn about those conflicts.
Assignee: nobody → smcarthur
Priority: -- → P2
Target Milestone: --- → Builder 0.9.5
Depends on: 658058
In the current state of 658058, we won't be able to include 1.0b5 _and_ receive the benefits of no longer conflicting on module names. So while b5 allows us to remove the warnings that the conflicts exist, the way for a user to overcome the conflicts is not supported by the Builder until SDK 1.0 includes a per-package mapper.
No longer depends on: 658058
Priority: P2 → P1
Target Milestone: Builder 0.9.5 → Builder 0.9.6
When a user uses the Add a Library modal, and selects a library to add, we should compare the packages dependencies and if there will be a conflict, prevent adding the library and show a red error message explaining the conflict.
Summary: Remove warnings about module naming conflicts → Show warnings when a user tries to add a library with conflicting library names
Severity: normal → blocker
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.