Community
Participate
Working Groups
In previous builds, there has always been a Europa Update site available in the Update manager. In build I20070524-0010, this seems to have disappeared.
Confirmed. I don't know why because the update sites still exist in the feature - this hasn't changed in months. Dejan?
This is very strange. When I set up the build for Update self-hosting, I can see the links in the second Eclipse instance, but not in the host eclipse. Notice another thing: when I open Manage Configuration link, no features show up except the root feature (no install locations). When I launch Eclipse from Eclipse, I can see these correctly. We need to find out when this stopped working and if there were changes in the runtime around that time -this looks to me like location URL resolution. URLs are somewhat different when launching Eclipse from Eclipse and install locations are found.
I tried I20070522-0010 and it works. Apparently this is very fresh.
Also works in I20070523-0010.
Got it - the problem first started in I20070524-0010. Kim, Update didn't make contributions to that build. We need to chase who did.
There were many contributors to this build - see http://dev.eclipse.org/mhonarc/lists/platform-releng-dev/msg09419.html I've compared the maps between these two builds and will attach a patch with the specific changes.
Created attachment 68701 [details] comparison of map files between I20070523-0010 and I20070524-0010
Without further insight, I would definitely start with the OSGi changes. JDT, text, compare, PDE etc. are too high up to affect Update Core.
Created attachment 68767 [details] Arbitrary update sites broken too Just to articulate it, this breaks any kind of update site. I added my own update site for my dynamic tools (pookzilla.net/dynamic) and I could not install the feature as it depended on org.eclipse.ui (which is invisible/unavailable/unclean/unflattering/whatevs)
Can someone point me to the code that populates the update sites? The only changes in OSGi from I20070522-0010 to I20070524-0010 was to the resolver. I'm not sure how that would effect update sites. You mention install locations. Maybe the launcher is not calculating this correctly. I need to do some more investigation.
Dejan, where did you get build i0523-0010? I can't find it on the web site. I tried 0522-0010 and it worked ok. I tried 0524-0010 and its broken. Unfortuanatly the releng project wasn't tagged for the 0522 build so its hard to compare the map file changes and post the diffs. A ton of projects changed, including update.core and update.ui.
I have i0523-0010 on my linux box so it must have been on the web site at one point. Confirmed that its also a problem on Linux.
Dejan, what about bug 179210? That's the only thing I can think of without digging into the problem.
fyi: dropping the i0522 update.core, update.ui and osgi into the i0524 build doesn't help.
How about startup code?
I replaced the launcher and exe and it is still broken.
According to Tom, there is a security exception - one of the JARs is corrupted because of the invalid SHA1 signature for file digest.html.
Tom figured it out (Tom, you are so smart!). It is com.jcraft.jsch_0.1.31.jar - it is corrupted. When I took 0.1.28 from 0522 and dropped it into 0524, it worked again.
One corrupt jar can cause this many problems?
I suspected the transition to JSch 0.1.31 was a bit to easy up until now. For RC2, we should just revert to 0.1.28. We can work out the JAR singing next week. However, I think it is clear that work needs to happen elsewhere. The JAR works fine in Eclipse so it would seem that Update (or someone else) is eating an exception that should be surfaced in some form (i.e. there is nothing in the log or anywhere else I could find). Is there already a bug tracking the silent exception or should we just move this one back to Update (or whoever).
I opened bug 189168 to track this issue in update. Update code is eating the exception and disabling the whole site for one corrupted bundle.
Reverted to previous version of jsch for next i-build, see bug 187296.
Verified that Eclipse and Europa update sites appear in I20070525-1350 as usual.
closing.
