Re: [ecf-dev] ECF API and feature freeze

[Markus Alexander Kuppe <ecf-dev_eclipse.org@xxxxxxxxxxx>]

On 05/08/2010 04:21 PM, Scott Lewis wrote:

> 0) I thought we had decided not to include the ZooDiscovery in ECF
> 3.3/Helios...due to the IP process delays.  I'm Ok changing that if
> that's the consensus, but

We decided not to include it in Helios due to the narrow time frame. But
now that everything is in place and there is still a chance to make it
part of Helios, I am +1 for getting it into.

> 1) What's the state of the IP approval process for the provider and lib
> dependencies?  (which seem to be Apache Zookeeper and log4j)

See 0) Everything has been approved already. :)

> 2) Markus if we are going to do this we should ask for exception from
> rt-pmc as soon as we decide to go this route (zookeeper discovery
> provider in Helios)

Will do once we have reached a consensus.

> 3) I see that one of the lib deps that Zookeeper has is log4j.  What
> version of log4j is needed?  Have you been using/developing against one
> of the log4j bundle's that's in Orbit?  One thing to watch out
> for...since log4j Orbit bundle is widely used by other projects, we want
> to make sure that whatever version of log4j that we include that it's
> compatible with whatever WTP and/or other projects use...and that our
> Zookeeper code works with what people may already have.

The dependency is towards Orbit's log4j version. The version I'm
currently using in my workspace is 1.2.15. But the org.apache.zookepper
bundle does not specify any version range at all.
Helios appears to ship 1.2.13 as well as 1.2.15.

> 4) Just FYI...I've fixed the license in the zookeeper feature...for
> consistency with the new license for Helios (i.e. bug
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=306627

Does this only apply to features or bundles too?

Markus