[FIXED JENKINS-12261] UI fix for checkout option
updated maven pom to use repo.jenkins-ci.org repository
On failing to branch a tree, assume that BZR has had a problem due
to not being crash safe in all situations (e.g. cancelling a build during
initial checkout) and wipe the tree and start again.

We've tested this pretty heavily at Percona and before this patch we pretty
much *had* to have "clean workspace" enabled (or clean the workspace very,
very often). With this patch, we have not had to do so ever again.
Merge pull request #8 from stewartsmith/master

Auto-recover on corrupted bzr repo
add my name and email to developer list in pom.xml
[maven-release-plugin] prepare release bazaar-1.18
Merge github.com:jenkinsci/bazaar-plugin
rollback pom.xml change from botched release attempt.
[maven-release-plugin] prepare release bazaar-1.18
[maven-release-plugin] prepare for next development iteration
Remove old maintainers from pom.xml so that they don't show on Wiki
add a README file
fix spelling of Trond's surname
Add .gitignore for target and work directories (used for packaging and debugging)
Clarify licensing of Bazaar plugin. It's the MIT license (same as Jenkins core). I've managed to contact nearly all of the contributors to ensure that they're happy with this.
Run a 'bzr revert' to ensure we have a clean checkout
and didn't hit the BZR bug where if you remove and then re-add
files/dirs with the same name when there are unknown files in the tree
then you get a conflict even with pull --overwrite

This is a workaround for a BZR bug.
fix docs for performing a release
[maven-release-plugin] prepare release bazaar-1.19
[maven-release-plugin] prepare for next development iteration
correct documentation for checkout: we were just doing a checkout, not a lightweight checkout. Thanks to Nathan Smith for spotting this