Thanks for the report. The pull request that introduced Assembla (this commit and this commit) missed a few files. I obviously didn't test it well enough (shame on me). The author corrected the mistake, but it was after the release of the 2.2.4 version of the plugin. It will be fixed in the 2.2.5 version of the plugin.

The commit which fixed it has been on github for almost two weeks (on both the master branch and the 2.2.x branch).

I'll release 2.2.5 within the next few days to fix that problem.

Fixed in git client plugin 2.2.5 released 15 Aug 2014

Thanks Mark - yes I assumed it was tiny mistake. Given enough users we see all bugs like that if it is likely to happen again - could a reflection based test look for the occurrence of appropriately named resources along with the classes? (if it is unlikely to happen again, don't bother).

I hope to eventually write a test which iterates through each of the extensions to the plugin, uses that instead in a config round trip test, and confirms that the extension correctly survives a config round trip. The existing round trip test does not enable any extensions, so it missed this test.

So much to test, so little time...