Need an idea on how to proceed here. There is a problem related to updating plugins here. We have renamed feature with one unrenamed plugin. How to we avoid problem when switching from org.spearce to org.eclipse One option is to release a v0.4.1 (which we should do anyway), which is the last version from master before the split. For technical reasons this will be a branch since the split occurred already. That 0.4.1 feature should require jgit < 0.5. Then we jgit to v0.5 and make org.eclipse.egit require jgit >= 0.5 Having two EGit features will be confusing. You get two of everything. E.g. Team>Share will have two Git's to choose from, but you cannot tell which is which. That said, having both could be a feature, since it (didn't really try it), would be possible to switch between new and old workspaces and get the plugin configured for that workspace. The wierdness make me suggest we do not do this. If we really want it we could choose to create a proxy plugin for attaching old workspaces to the new plugins. -- robin -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html