Closed
Bug 1016050
Opened 10 years ago
Closed 10 years ago
jpm should include an option to run the Add-on debugger
Categories
(Add-on SDK Graveyard :: General, defect, P2)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: wbamberg, Assigned: evold)
References
Details
Attachments
(2 files)
At the moment working with the Add-on Debugger and cfx is cumbersome. I need to call cfx run, then when the browser is up go to Tools/Add-ons, switch to "Extensions", click "Debug", and confirm the warning dialog. It would be great if I could just do something like "cfx run --debug" and have the debugger launched automatically. This might be a better fit for JPM than cfx though.
Comment 1•10 years ago
|
||
This is an awesome idea. Let's confine it to jpm though, we have no intention of releasing another version of cfx.
Reporter | ||
Updated•10 years ago
|
Summary: cfx/jpm should include an option to run the Add-on debugger → jpm should include an option to run the Add-on debugger
Comment 2•10 years ago
|
||
+1!
Updated•10 years ago
|
Priority: -- → P2
Comment 3•10 years ago
|
||
I still think this is an awesome idea, but it should not block releasing jpm beta.
Assignee | ||
Comment 4•10 years ago
|
||
Can I implement this in the addon/runner module, as the last step? basically I would check if the load command was "run" and the "debug" option was provided, then open the debugger. Another option is to do this in the bootstrap, or as a Fx cmd line arg
Flags: needinfo?(rFobic)
Assignee | ||
Updated•10 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Comment 5•10 years ago
|
||
(In reply to Erik Vold [:erikvold] [:ztatic] from comment #4) > Can I implement this in the addon/runner module, as the last step? > basically I would check if the load command was "run" and the "debug" option > was provided, then open the debugger. > > Another option is to do this in the bootstrap, or as a Fx cmd line arg I think FX CMD line sounds best of all, although there maybe some caveats. I'll leave it up to your judgment to decide which option will work the best, either one sound reasonable.
Flags: needinfo?(rFobic)
Assignee | ||
Comment 6•10 years ago
|
||
Attachment #8481866 -
Flags: review?(jsantell)
Assignee | ||
Comment 7•10 years ago
|
||
Attachment #8481867 -
Flags: review?(jsantell)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → evold
Updated•10 years ago
|
Attachment #8481866 -
Flags: review?(jsantell) → review+
Comment 8•10 years ago
|
||
Comment on attachment 8481867 [details] [review] Link to Github pull-request: https://github.com/mozilla/jpm/pull/159 r+ with the comments in the PR addressed (clarify help description for `--debug` and add the command option in the README)
Attachment #8481867 -
Flags: review?(jsantell) → review+
Comment 9•10 years ago
|
||
Commits pushed to master at https://github.com/mozilla/addon-sdk https://github.com/mozilla/addon-sdk/commit/712e356edf42b570b4500ba15bb985288d2e2cc9 Bug 1016050 - jpm should include an option to run the Add-on debugger https://github.com/mozilla/addon-sdk/commit/d9b147bf4a2ae86e3b53ef329b3c31683cefa151 Merge pull request #1604 from erikvold/1016050 Bug 1016050 - jpm should include an option to run the Add-on debugger r=@jsantell
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•