What caught us off guard was not the bugs with the new P2
mechanism, but the fact that we expected classic Update Manager to continue
working, since this is claimed with no limitations are listed:
http://wiki.eclipse.org/Equinox_p2_Getting_Started#Interaction_with_legacy_Update_Manager
I know that it’s annoying that we’re complaining and
filing all these bugs after M6. But plain Mylyn installed fine, it was the
external Mylyn integrations which rely on things like associate sites and
htaccess that broke.
In terms of expectation, we would like to be able to tell our integrators
when the update mechanism will be usable for them again so that they can resume
consuming Eclipse 3.4 M/RC builds. The bugs that we care about in this
respect, and have been testing with I-builds, are all listed below. For
making classic Update Manager work I believe the only one left is bug 225054.
We’ll continue testing and posting on the corresponding reports.
Mik
From:
cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of John
Arthorne
Sent: Friday, April 11, 2008 2:32 PM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] the state of update
I'm not sure
what kind of response you're expecting here... By "fully functional"
do you mean completely free of bugs, or that all the bugs listed below will be
fixed, or what? The goal of M7 is to produce a stable build in which all major
feature work for 3.4 is complete. After that, there will be another month of
test/fix passes after M7 before the 3.4 release. If there are bugs you care
about, you can increase the chance of them being fixed in the usual ways: make
sure you enter bugs, provide details, grab the I-builds and test, etc.
John
Mik Kersten wrote on 04/11/2008 02:21:37 PM:
> On Mylyn we have had a challenging time with the 3.4M6 update changes
> because P2 doesn't work for all the cases that we need to support, and
> classic Update Manager behavior cannot be fully restored.
Ideally it would
> be great for P2 to handle all previous update cases, but for the time
being,
> can we expect the old Update Manager to be fully functional in 3.4M7?
>
> To save others in this situation time in figuring out what works and
what
> doesn't, here is our summary of the problems present in 3.4M6 and M6a.
>
> ----------------------
>
> Problems with classic Update Manager in M6a:
>
> * Extensions are installed into the configuration directory and never run
> (bug 221434, looks like it's fixed in HEAD)
> * Platform.xml gets put into the wrong directory due to URL encoding
(bug
> 225054, may also affect P2)
> * Extensions installed into an extension directory do not run (fixed
in
> I20080410-1022)
>
> Summary of problems with P2 in M6a:
>
> * Downloading too many plug-ins causes OutOfMemory (bug 226206)
> * Htaccess protection of sites causes deadlock (bug 220554, partly
fixed in
> I20080410-1022 but we are still seeing deadlocks)
> * Associate sites get ignored (bug 220554)
> * If associate sites or other sites have overlapping categories they
may get
> ignored (still checking and will file bug)
> * Included features are not nested properly and may not be included
(still
> checking and will file bug)
>
> Mik
