Community
Participate
Working Groups
Build Identifier: 20100917-0705 Hi, Would it be possible to somehow share the *same* workspace project to multiple, differing, Team providers, such as Git (EGit) *and* CVS, concurrently, i.e making the Team menus available for both. Basically, I've a requirement to maintain both Git and CVS repository information within the same project. The idea here is that we could use Git/EGit plugin to branch code etc., while maintaining use of Eclipse CVS Team synchronisation for direct commits to our existing (and yet to be decommissioned) CVS server. I am in the process of introducing the benefits of Git-based development to my department, however, there are many that are wary of new tools or who do not wish to go to the command-line during development (added to which, visual tools are usually a good thing). Reproducible: Always Steps to Reproduce: 1. Share the project via the Team menu option. 2. No further opportunity to share the project again is offered.
I had a chat with Szymon and we decided to mark this bug as WONTFIX since we do not plan to fix it. You are free to reopen the bug if you don't think this is an acceptable solution. However, this will mean you're willing to work on it. Of course, we're offering our help in case anyone picks this one up.
I think you could use the same CVS-to-git transform that the Eclipse Foundation uses. Then your new work on branches can be done against the git repo, and your main work can be turned into patches that can be checked into CVS. I found it a bit of manual work, but it allowed me to use Git while the CVS is still the main repo. Note: CVS-to-git is less robust than SVN-to-git, which sees more use. PW
I remember that when read-only mirrors of Eclipse CVS repositories[1] showed up I was very excited to give it a try. My setup looked like this: I had 2 workspaces, one for projects checkout from CVS repo via extssh (write access), another with git clones from [1]. When working with the second workspace I created branches for each bug I was working with and when done I put up a patch which I applied in the first workspace and then committed to CVS HEAD. This worked pretty well, except the create/apply patch stage which was cumbersome. Another option is to checkout a project from CVS, using CLI init it as a git repo and ignore .git folder in CVS. This way you could work with git using CLI and when done, switch to Eclipse and commit your changes with CVS UI. You could also try to switch team providers by disconnecting from CVS (without deleting the meta-data folders) after you have checked out the project and then sharing it with a git repo. When done you could disconnect from git, switch back to CVS and commit to the CVS repo. If I haven't missed anything all these operations can be done without leaving Eclipse. [1] http://dev.eclipse.org/git/index.html
Hi, I would like to at least reopen the list of arguments on that topic: I use two differen Teamprovider for different functions. On the one side I use Git for Version Controll, and on the other side I use the ABAP Repository Team Provider (SAP) to be able to publish my code into the system hosting the final application. In that second usecase there is no Version Controll involved/intended, therefore it would be a great help to have two or more Teamprovider active on one Workspace-Project. Since the second usecase is a output-only Szenario, I could imagine to have secondary Teamproviders working as "Deployment-Plugin" with the syncing only working one direction from Eclipse to outside. BR, Tim
