Add-ons built with jpm 0.0.25+ should fail hard on Firefox <= 37

[jeffgca]

Currently if you package an add-on with jpm 0.0.25 and run it anything less than Firefox 38, it fails silently, see this stackoverflow report.

We should detect Firefox <= 37 and alert the user somehow. Does compatibility ranges work? Or throwing an exception.

[erikvold]

Ah we can do this by making the min supported version Fx 38

[tomsaen]

I came to the same problem, although I used the newest Nightly of Firefox (version number right now: 38.0a1). The fix that involes updating the MIN_VERSION to "38.*" did not work for me. The FF always states, that this addon is not compatible with this version of FF. Changing the MIN_VERSION to "38.0a1" fixed this issue for me.
I'm not sure if this happens only for me, I just thought I would share this experience.

[bhollis]

This is pretty ridiculous, guys. jpm is clearly half-baked. If it can't produce extensions that work on older Firefox (which is crazy already), it should also not allow generating an install.rdf that purports compatibility with older Firefox.