Closed Bug 552849 Opened 14 years ago Closed 10 years ago

make cfx warn users if they haven't yet activated SDK

Categories

(Add-on SDK Graveyard :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: myk, Unassigned)

References

()

Details

In this forum post <http://groups.google.com/group/mozilla-labs-jetpack/msg/bdadcdae658e9753>, Mike7 writes:

----------------------------------------------------------------------
I'm wondering about a couple of problems with cfx.bat.  If I execute
it without modification, Python seems to try to open ...\bin\bin\cfx
and fails due to "No such file or directory."  If I edit \bin out of
cfx.bat and try cfx test, the following message appears:

Traceback (most recent call last):
  File "c:\jetpack-sdk-0.1\bin\cfx", line 3, in <module>
    import cuddlefish
ImportError: No module named cuddlefish

I'm using Windows Vista and don't know whether these are bug-related
problems or not.
----------------------------------------------------------------------
Thanks for reporting this. This problem seems symptomatic of not having run 'bin\activate' before running 'cfx', though I've mentioned in my reply that we might want to add some basic error-checking to the .bat files which displays an error if the CUDDLEFISH_ROOT environment variable (created by activate.bat) isn't defined:

  http://groups.google.com/group/mozilla-labs-jetpack/msg/87e62104410ab1e9

We could make a separate bug for this, to improve the user experience for developers. To work for OSX/Linux, we'd also have to put in some error-checking code at the beginning of all the python scripts in the 'bin' directory too.
Ok, let's make this bug be about adding a warning to cfx that notifies users when they try to run cfx without having first activated the SDK.
Summary: ImportError: No module named cuddlefish running |cfx test| → make cfx warn users if they haven't yet activated SDK
Target Milestone: -- → 0.3
Given that no one is working on this, it seems unlikely to make 0.3. 
Retargeting to future until we can triage to a specific milestone.
Target Milestone: 0.3 → Future
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
Priority: -- → P3
Does this still occur with the current versions of the SDK?
Target Milestone: Future → 1.3
(Pushing all open bugs to the --- milestone for the new triage system)
Target Milestone: 1.3 → ---
Yet another wontfix possiblity due to bug 915376
Flags: needinfo?(dtownsend+bugmail)
I agree, as a rule though I tend to keep bugs open until the thing that obsoletes them has landed.
Flags: needinfo?(dtownsend+bugmail)
Sorry we won't be releasing any new versions of cfx, jpm is the replacement https://www.npmjs.com/package/jpm
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.