Community
Participate
Working Groups
Build Identifier: The GIT mirror repository for Eclipse Riena seems to lack some essential commits when compared to its CVS counterpart. As a result, the Riena build process will fail if sources are imported from GIT instead of CVS. Example of a commit that seems to have been lost during cvsimport (it has no GIT equivalent): http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.riena/org.eclipse.riena.ui.core/plugin.xml?revision=1.3&root=RT_Project&view=markup Since this problem seems similar to #307273 in nature, re-creating the GIT repository from CVS might be the only way to go. Reproducible: Always
By now, we've managed to work around the problem by setting-up our own custom GIT mirror of the Riena CVS repository using GIT 1.7.1 and CVSPS 2.1 (the resulting GIT repository seems to contain all CVS commits that the official Eclipse GIT repository is currently lacking). Still, I strongly recommend that someone at Eclipse re-creates the repository from CVS using an up-to-date version of GIT and CVSPS. In its currently shape (missing some commits here and there), the mirror will otherwise only serve to confuse people, since no one would honestly suspect a flaw in their version control system to be the root cause behind a given compile or run-time error. I know, because I didn't :-)!
I've deleted the repo and I'm re-creating it with git 1.7.1
(Adding us Riena committers to CC)
Christian, I've re-created the repo. Can you confirm if it is sane?
Denis, looks ok to me. @Christian: BTW I think we should ask Denis to remove some obsolete projects from Riena CVS. It's confusing for git, because you get a full clone of the repo with all the obsolete (and non-compiling) stuff. Will move this discussion to the mailing list...
Great, I'll close this as fixed. Please open a bug against Community/CVS if you want some cleaning-up.