[equinox-dev] Issues with upgrading from I20131119-0800 or earlier

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[equinox-dev] Issues with upgrading from I20131119-0800 or earlier

From: Thomas Watson <tjwatson@xxxxxxxxxx>
Date: Thu, 5 Dec 2013 08:34:36 -0600
Delivered-to: equinox-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/equinox-dev>
List-help: <mailto:equinox-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/equinox-dev>, <mailto:equinox-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/equinox-dev>, <mailto:equinox-dev-request@eclipse.org?subject=unsubscribe>

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

Prev by Date: Re: [equinox-dev] Strange Heap overflow with Luna M3
Next by Date: [equinox-dev] TrustEngine in supplemental?
Previous by thread: [equinox-dev] Strange Heap overflow with Luna M3
Next by thread: [equinox-dev] TrustEngine in supplemental?
Index(es):
- Date
- Thread

Breadcrumbs