[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [p2-dev] ECF p2 repos are missing
|
On 10/26/2010 8:02 PM, Jeff McAffer wrote:
So is this a problem of repo stability? Seems like all ECF (whatever
project) consumers would have a problem if there is reduction in the
stability or durability of the project repos. Personally I encourage
all projects to declare and maintain repo durability and URI stability
models that facilitate their consumer usecases. If repos are moving
and disappearing randomly, the project will be seen as unstable or
hard to adopt and consumers will just go away.
Do we expect that this will be an ongoing problem?
No. It's due to a miscommunication around moving these integration
bundles to archive.eclipse.org in response to EF clean up request. See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=328511
The ongoing problem is that the current process for us to make the
filetransfer plugins available to the platform is unsustainable for us.
It complicates the build of other parts of ECF (i.e. that are not
consumed by the platform but rather distributed as part of ECF), and the
releng we've been doing to accomodate the platform build creates a lot
of unnecessary work for us. We have don't have enough resources to
waste them.
We would like to move to a model where we build all our bundles with our
builder, produce a p2 repo, and the ECF filetransfer bundles are
consumed by the platform from that repo. That seems doable to me...as
it should be possible for the platform releng to simply read/retrieve
the relevant (filetransfer) bundles from out of the repo created by our
builder....rather than what we are doing now with map file
entries...which is clumsy, error prone all around, and costly for us.
Scott