So there were a bunch of e-mails flying
around with how to best handle the ICU dependency issue for Galileo, whether
by using import package or bundles in the plugin metadata. We adjusted
the DTP plug-ins to change the upper bound of the bundle version constraint
to 5.0 (from 4.0), but it came up yesterday that perhaps we should just
remove all version constraints or go with the import package method...
I'm wondering what the general consensus
is for this... Are we being asked to import the ICU packages into each
plug-in where ICU is being used? Or are we simply removing the version
bounds? What is the suggested course of action?
Thanks in advance. Sorry if I'm clueless
on this, but I thought I'd bring it up to the council at large so I can
get the right information to take back to my PMC and team leads. If it's
easiest just to point me somewhere, I'll be happy to skulk quietly back
into the corner. :)
Eclipse Data Tools Platform PMC Chair
Eclipse Data Tools Platform Connectivity Team Lead
Staff Software Engineer, Sybase, Inc.
Richard Gronback <richard.gronback@xxxxxxxxxxx> Sent by: eclipse.org-planning-council-bounces@xxxxxxxxxxx
01/27/2009 09:14 AM
Please respond to
Re: [eclipse.org-planning-council] Agenda
item for Feb 4 Call
Thanks, I created a page and added this topic:
On 1/27/09 5:07 AM, "Oisin Hurley" <ohurley@xxxxxxxxxxxx>
> Antoine, the project lead of the BPMN Modeler Project,
> would like the Planning Council to consider the following
> proposal for the Galileo release train projects.
eclipse.org-planning-council mailing list
IMPORTANT: Membership in this list is generated by processes internal to
the Eclipse Foundation. To be permanently removed from this list,
you must contact emo@xxxxxxxxxxx to request removal.