Community
Participate
Working Groups
This bug is well described in bug 380880. I'm opening this bug in Orbit to "do the fix" (when its done) and then 380880 can be used to "pick up the fix" when its ready.
I don't consider this bug a "blocker" ... but, suggest we be "ready to go" in the rare event some other blocker would be found then we _might_ want to fix this one too. Normally I wouldn't, but, being in "the Platform" sort makes it visible everywhere. Its doubly unfortunate since it is first in the list of bundles without proper name in the common repo report: http://build.eclipse.org/juno/simrel/reporeports/reports/bundleNames.html (and, yes, somewhere there is a bug to add those reports directly to Orbit too ... would have been done by now ... but ... got distracted :)
FYI, see also bug 380985 which lists the 15 or 17 problematic cases in current (Juno) repo.
Fixed released to 1.8.3 branch. I won't mark a milestone on this bug until we decide which build it is included in.
The problem is still in Eclipse SDK 4.2.x M20120816-1200 Shouldn't this be fixed for Juno SR1 ?
I asked Dani in bug 380880 and the view was not. Unless there was a functional reason to produce a Juno SR1 (beyond this "cosmetic" reason). I agree the name/label does not normally rise to the level of "maintenance" (but I'm sort of 30/70 on the issue, so if you think it is very important, and get a few people to agree with you :), I'd suggest you open a new bug to "produce Orbit Juno SR1 release", and post to orbit-dev list to see if there is any discussion pro or con. It is extra work for me, but if many thought it was important, I suspect I could fit it in. But, we are running short on time, should do in the next week, if we are going to; that is, should be done before RC2. Thanks for asking.
