[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [orbit-dev] Addind/Updating Libaries in Orbit
|
Hi Gunnar,
that's quite a bunch of 3rd party dependencies.
Have you checked (with PMC or projects providing
related technology) whether these are really
needed and choosing these is the right thing
to do?
Approving such a big bunch of code is a whole
lot of effort, and I think it's worth first
making sure it's the right technical thing
to do. I guess this step is what the required
PMC +1 vote on CQ's is good for...
Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
> -----Original Message-----
> From: orbit-dev-bounces@xxxxxxxxxxx
> [mailto:orbit-dev-bounces@xxxxxxxxxxx] On Behalf Of Gunnar Wagenknecht
> Sent: Friday, November 07, 2008 9:49 PM
> To: orbit-dev@xxxxxxxxxxx
> Subject: [orbit-dev] Addind/Updating Libaries in Orbit
>
> Hi Orbit Committers,
>
> For our CloudFree project I need/want to update/add content
> to the Orbit
> project. The purpose of this mail is to socialite feedback from you on
> the approach/steps to take.
>
> These are the dependencies which I can't satisfy from Orbit:
> Apache Solr 1.3 (including SolrJ Client)
> Codehaus Jackson
> Google Web Toolkit 1.5.3
> Apache Commons CSV
>
> Required by Solr:
> Apache Lucene 2.4
> StAX Utils (https://stax-utils.dev.java.net/; I asked on the Solr dev
> list if that dependency could be made optional)
>
> Should I first submit individual CQs for my project and then for Orbit
> or should I first submit CQs for Orbit and then for my project
> indicating re-use from Orbit?
>
> Is it ok to submit one CQ which results into multiple Orbit
> bundles? For
> example, Solr is provided as one single zip. It includes the full
> source. However, for Orbit it would make more sense to split it across
> different bundles (eg. solr.common, solr.core, solr.servlet,
> solr.client.solrj, solr.client.solrj.embedded) which allows a
> more fine
> grained consumability and clearer dependencies in manifests.
>
> Lucene is already in Orbit but in an older version. I also found out
> that the bundle in Orbit is missing the org.tartarus... packages. It
> seems like there need to be separate CQs for the various Lucene
> contribute source. There is actually CQ2603 but that's for the old
> version too.
>
> -Gunnar
>
>
> --
> Gunnar Wagenknecht
> gunnar@xxxxxxxxxxxxxxx
> http://wagenknecht.org/
>
>
