Thursday, April 07, 2011

Google code Mercurial SCM / issue-tracker integration

I just patched a littleware bug, and I wondered whether Google code had some SCM integration with its issue tracker, so that I could update the bug's issue with the patch's commit message. The answer is yes ! One limitation is that the SCM message only propagates to the issue-tracker after being pushed to the main Mercurial repository - pushing to a clone won't do it. That's probably the best way to implement the feature anyway.

I posted a new littleware download bundle online today too. The new code includes openId support, and separates out the base littleware ivy module from a new littleAsset module that also includes the old littleApps module. That probably sounds meaningless, but basically I pushed the code around, so that an application can more easily link against the littleware.base packages without also dragging in the littleware.asset stuff that a lot of apps don't need.

Anyway, I'll try to put together a "release notes" bLog post soon with more details on the openId stuff. I intend to get back into the discipline of updating the bLog at least once a week - there's always something to talk about. For example, I actually have a little openid-helper web service that I want to get up online with Amazon web services. I'm not sure whether the openId helper is really all that useful, but AWS is giving away 12 months of free use, so I might as well give it a try - see what the fuss is about.

Post a Comment