jetpack changed its xpi model

Issue #16 resolved
Zibi Braniecki
created an issue

After some changes to the XPI model of AddonSDK, we cannot rely on package.json anymore.

You can get an example XPI by going to and clicking Download

We should read the required metadata (jetpackID, fullName, version?) from it and then combine the path to the directory that we will be scanning for entities basing on that (resources/JetpackID-name-lib/).

Comments (3)

  1. Zibi Braniecki reporter

    ok, it seems that the metadata required to read the main jetpack is available in harness-options.json - can we switch to use that? It's critical as it blocks us from using the service with jetpacks built in the builder.

  2. Log in to comment