Phil Beauvoir

Setting the property "-Djgit.gitprefix=\" location in the Archi.ini file might be a workaround. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=515354#c24

We can't change it because it was hard coded as the primary branch years ago. If we tried to change it now, it would lead to unpredictable results and backward-compatibility...

Thanks, I'll take a look at this.

Sorry, but that's out of scope for the collaboration plug-in, as the repo should only contain model information. A better way to do this is to generate and publish an...

Will investigate options in the next coArchi coDing sprint.

We need the organisation that we have in jArchi.

As History and Branches are so closely connected I thought that it might be better to keep them together visually in the same Eclipse View:  Before proceeding can we...

Branches exist locally and/or online. How do we want to handle that logically and in the UI? Here's how SmartGit does it for local and remote branches and tags: 

If we're going to have tags as well then I think we need to do as SmartGit does it with a tree of three things - Remote branches, Local branches...

If branches are in the Collaboration view, the user will always need to have that view and the History view open to switch branches and see the updated list of...