Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [orbit-dev] Addind/Updating Libaries in Orbit

Gunnar, I'll gladly take Apache Lucene 2.4 to Orbit. I haven't convinced the Platform to move to Lucene yet, but if you want to make the case, here is the bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=248986

It would be nice to not have redundant dependencies that affect downstream consumers.

I noticed that Apache Commons CSV doesn't have an official release yet... what version number would be used?

I don't mind handling the Apache libraries in Orbit.

On Fri, Nov 7, 2008 at 2:48 PM, Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx> wrote:
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/


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




--
Cheers,

~ Chris Aniszczyk

Back to the top