| Re: [eclipse-dev] Issues with upgrading from I20131119-0800 or earlier |
|
I know I saw strange behavior when doing the upgrade, but I did not try any p2 operations. If a -clean operation fixed the issue then that is an indication that something went wrong with the resolution of the bundle after the upgrade. So it does seem likely that this was a side-effect of the fragment resolution issue that I was seeing. If folks are seeing strange things they can start with -console and see if any fragments are not resolved. If so then run with -clean. Hi Thomas, When I upgraded to I20131126-0800 last week I started running into strange issues with update sites: "Error while reading from repository". It also affected target definitions that use p2 update sites. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=423004 I ended up "fixing it" with -clean. Do you know if that's related to the issue you are talking about? Thank you, Marc-Andre On 13-12-05 09:34 AM, Thomas Watson wrote: I ran into an issue doing a build to build upgrade from I20131119-0800 or earlier to the latest I-Build. The symptom is that many fragments may end up not resolved. This is a side effect of a fix put in for bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=421706 I have fixed the issue for the next I-Build. In the mean time, if you are doing build to build upgrades then the work around is to issue is to start eclipse with the -clean option after updating in order to force regeneration of the persisted bundle metadata. Sorry for the inconvienence. Tom
eclipse-dev mailing list eclipse-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/eclipse-dev |
