Closed
Bug 545271
Opened 14 years ago
Closed 14 years ago
treat main.js as "main" module if not otherwise specified
Categories
(Add-on SDK Graveyard :: General, defect, P3)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
Future
People
(Reporter: myk, Unassigned)
Details
If a manifest.json file for a package doesn't specify a "main" module, and a module with the name main.js exists in the package, Jetpack should treat that module as the "main" module.
Reporter | ||
Updated•14 years ago
|
Priority: -- → P3
Target Milestone: -- → Future
Comment 1•14 years ago
|
||
Fixed: http://hg.mozilla.org/labs/jetpack-sdk/rev/c3fa261d5d7c Wanted to get this in before 0.1 so the tutorial is shorter; with less things to do, there's less room for the user to mess up and get confused/frustrated.
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 2•14 years ago
|
||
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product. To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
You need to log in
before you can comment on or make changes to this bug.
Description
•