bzr-eclipse does not integrate with bzr whoami command

[Alexander Taler]

On the bzr-eclipse preferences page:

  Window -> Preferences
  Team -> Bazaar

the User id/email setting specifies the value set in the Committer field when committing.

However, the Bazaar command-line client uses a different mechanism for specifying this field: bzr whoami.

Ideally bzr-eclipse would store this value in the same location as bzr whoami so that they can work on the same tree with the same results.

[Piotr Piastucki (piastucki)]

Handling whoami seems to be a bit tricky as there might be multiple branches used in a single workspace.
Some ideas:
1) It is quite convenient to have a separate setting on a per-workspace level that is unrelated to stored bzr settings as it is possible to use different identity for each workspace. I do not think we should change global whoami setting from bzr-eclipse.
2) A new 'whoami' action might be added to Team menu to view/change the settings on a per-branch level
2) id/email field in preference page can be by default populated with global whoami setting. If nothing set, bzr-eclipse should fall back to system username. Additionally, there can be a checkbox to disable the field. When it is disabled Bazaar will decide what to use based on whoami settings in particular branches/projects or global whoami settings.

[Piotr Piastucki (piastucki)]

Fixed. By default "User id/email" field will be populate with the value returned by bzr whoami unless the value cannot be retrieved. In this case the code will fallback to system user name as before.