Closed
Bug 557316
Opened 15 years ago
Closed 14 years ago
Add --version option to the cfx command line tool
Categories
(Add-on SDK Graveyard :: General, enhancement, P2)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 704519
People
(Reporter: fiveinchpixie, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: jetpack-sdk 0.2rc2
There is currently no way to determine from the command line which version of the jetpack-sdk/cfx tool that is currently being run.
Reproducible: Always
Expected Results:
(jetpack-sdk)pixie$ cfx -V/--version
should return the version of the cfx tool currently being used.
Comment 1•15 years ago
|
||
We should fix this soon after 0.3 (0.4?).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: -- → Future
Comment 2•15 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
Version: 0.2 → unspecified
Updated•14 years ago
|
Priority: -- → P3
Target Milestone: Future → 1.0
Comment 3•14 years ago
|
||
(automatic reprioritization of 1.0 bugs)
Priority: P3 → P2
Target Milestone: 1.0 → 1.1
Comment 4•14 years ago
|
||
Note that the version is currently stored in the .version file at the top-level of the SDK, and that's probably where the --version flag should retrieve the value from.
Re-prioritizing all 1.1-targeted feature requests to 1.2.
Target Milestone: 1.1 → 1.2
(Pushing all open bugs to the --- milestone for the new triage system)
Target Milestone: 1.2 → ---
I believe bug 704519 does this. Someone correct me if I'm wrong, though...
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•