Switch from 'cfx' to 'jpm' for packaging

[whimboo]

Looks like the cfx tool is going to be replaced with jpm. So we will have to change our code accordingly. See the blog post from Eric: http://work.erikvold.com/jetpack/2014/08/07/cfx-to-jpm.html

Targeting for the 0.7 release.

[xabolcs]

If nobody works on this, I would like to take it!

@whimboo could you assign me for this issue?
I could continue with this after the Australis UI/Toolbar fix.

[xabolcs]

Slightly related post: Node.js as a build script

[whimboo]

Thanks @xabolcs! Btw. you can assign yourself to any issue you want. You should have the permissions to do so. :)

[xabolcs]

You should have the permissions to do so. :)

Interestingly I'm unable to do so.

[whimboo]

Hm strange. Anyway lets get this discussed on IRC when you have time. Thanks for noting it.

[xabolcs]

This needs two step.

1. entry point in package.json
2. loading modules from test modules (see MDN page)

The second breaks cfx, so we need to migrate .travis.yml and build.xml too.

But at least 21 of 21 tests passed. :)

[whimboo]

Sounds fine to me. Especially if all tests are still passing.

[xabolcs]

FYI JPM Replaces CFX For Firefox 38.

[xabolcs]

It would be nice to do this migration when next ESR become public.

[xabolcs]

See those failed Travis builds for Nightly 45.0a1 and Aurora 44.0a2!