[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] [p2] ECF bundles not up to date in M6

Hi Pascal,

Strange...as I'm quite certain I checked 3/31 afternoon that the jars referenced in this map


were replicated OK. Even so, this was after M6 build (sunday) anyway.

But this brings up a question for us: If people use the dropins and/or plugins directory install, and they put a newer version of a plugin that already exists/is installed as part of platform, what happens? Bad things/is this to be avoided? or can it be safely done?



Pascal Rapicault wrote:
I'm sorry about the problems this can cause the ECF users, however we tried
moving to this most recent build but as you can see, it failed finding the
jars on the server during the build

In case of a rebuild we will be looking into addressing this.

From: Scott Lewis <slewis@xxxxxxxxxxxxx> To: Equinox development mailing list <equinox-dev@xxxxxxxxxxx> Date: 04/01/2008 09:38 PM Subject: [equinox-dev] [p2] ECF bundles not up to date in M6

Howday p2'ers,

The M6 release of Eclipse/p2 seems to have used a relatively old
integration build of the 4 ECF bundles (i.e. they have qualifier
v20080317-0809 rather than the 20080324 integration build as I expected
from this bug:


This is not tragic, but it causes us a little bit of consternation
because there were some very small API additions for ECF filetransfer
during the week of the 17th, and these obviously didn't get into M6 of

This means that the next milestone of ECF will include these small API
additions...and I wanted to let everyone know this doesn't constitute an
API freeze breach...as ECF's filetransfer bundles are frozen at this
point (but M6 of platform didn't get these additions during week of 24th).



_______________________________________________ equinox-dev mailing list equinox-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/equinox-dev

equinox-dev mailing list