Community
Participate
Working Groups
Using the SDK build from I20111027-1910 I I tried to "import from repository" for all bundles. (I used "version tag" option, not HEAD). This "worked" for 21 bundles. The rest, presumably, don't have valid one Eclipse-SourceRefernce directives ... at least not for CVS. (If I recall right, the "import from repository" for Git has not been implemented yet). Of those 21, 7 were from Orbit ... all is fine and well there. But, I was surprised about the 14 others, as I thought all of Eclipse SDK bundles were now in Git. I'll paste the list of 14 below, but my guess would be these bundles have not changed since migrating to Git, so the mirror-with-comparator operation picks the "old" one to include in the build. If that's all true, then technically speaking, it is probably still "accurate" since it can get the old cvs version from the read-only repository. But ... also is sort of wrong if development is not going on from CVS ... people could not supply patches using that, for example. If that is true, then I suspect the bundles below should be "re-tagged" so new versions get picked up that do not have the Eclipse-SourceReference in them pointing to CVS? Naturally, this report would be invalid if these 14 _are_ still being developed from CVS. Can't say its a big problem, this early in cycle ... but ... I hope you find this report helpful. org.eclipse.core.filesystem.linux.x86_64 org.eclipse.cvs org.eclipse.platform.doc.isv org.eclipse.platform.doc.user org.eclipse.rcp org.eclipse.sdk org.eclipse.core.contenttype org.eclipse.core.expressions org.eclipse.core.net.linux.x86_64 org.eclipse.core.runtime.compatibility.registry org.eclipse.core.variables org.eclipse.pde.build org.eclipse.platform org.eclipse.update.configurator
Yes, David, that's the issue, the bundles haven't changed since we moved to Git. A few of the features rcp, sdk are still in CVS. We will wait to tag them until source reference generation is fixed for Git. See bug 327381
Is this still an issue ? See recent discussion on https://bugs.eclipse.org/bugs/show_bug.cgi?id=421321
No, not still an issue. I suspect was fixed in "Juno 422", though I only checked a recent "M-build", so I'll mark as fixed in 4.3. Thanks for the comments in bug 421321.
