Community
Participate
Working Groups
Here is the test repo that I created ssh://userid@git.eclipse.org/gitroot/jdt/eclipse.jdt.debug.git Let me know if you have any issues that I need to address for the real migration. Also, if you could verify the branches for org.eclipse.jdt.launching* that would be great. There was some old cvs files that pointed to the zrh cvs server from OTI days which was weird and caused strange error message. (We used to use csvup to sync files from zrh to dev.eclipse.org because the Zurich lab had limited bandwidth).
Everything looks good from what I can see. The only thing I would request is that we do not migrate the org.eclipse.jdt.launching.j9 bundle to git - reason being, (1) this bundle has never been part of a build, (2) has not been worked on for many years and, (3) the only way to get the support for the bundle is to get the old source and build it yourself.
Sure, that sounds fine. I'll exclude it when I do the migration.
> (3) > the only way to get the support for the bundle is to get the old source and > build it yourself. How can I build it (i.e. get the source) when the CVS servers are removed?
(In reply to comment #3) > > (3) > > the only way to get the support for the bundle is to get the old source and > > build it yourself. > How can I build it (i.e. get the source) when the CVS servers are removed? You would build it from the archived CVS or we could archive it and put it on the debug website / wiki
(In reply to comment #3) > How can I build it (i.e. get the source) when the CVS servers are removed? I have provided a pre-built version of the J9 launching support which includes the source here: http://wiki.eclipse.org/Debug/FAQ#J9_JRE_Support and here:http://www.eclipse.org/eclipse/debug/j9/j9_launching.php
I think we are ready to proceed with the real migration.
Okay great, you may know already, the PMC has asked me to hold off migrating JDT until 3.7.1 ships.
(In reply to comment #7) > Okay great, you may know already, the PMC has asked me to hold off migrating > JDT until 3.7.1 ships. Yup, just indicating our ready-ness for the migration.
Your actual migration has completed, your repo is ready ssh://userid@git.eclipse.org/gitroot/jdt/eclipse.jdt.debug.git
(In reply to comment #9) > Your actual migration has completed, your repo is ready > > ssh://userid@git.eclipse.org/gitroot/jdt/eclipse.jdt.debug.git Just tried cloning it and got an error about no repo existing
Sorry about that, try again, I've fixed that.
(In reply to comment #11) > Sorry about that, try again, I've fixed that. Looks good now, I have cloned the repo and pushed some changes. Closing as fixed.
I noticed that the debug map files still point to CVS. Could you update them to point to Git? If you want to run a test build to verify the changes, you can run this test build https://hudson.eclipse.org/hudson/view/Eclipse%20and%20Equinox/job/eclipse-equinox-test-N/
I updated the map file and just started a test build: https://hudson.eclipse.org/hudson/view/Eclipse%20and%20Equinox/job/eclipse-equinox-test-N/374/
verified a while back...
