Re: [orbit-dev] Apache POI

[David M Williams <david_williams@xxxxxxxxxx>]

Edwin, 

You've taken the right first step ...
posting to this list. :) 

From here, there's two possible paths.


1) You can become a committer in Orbit
yourself (assuming you are a committer in Nebula or NatTable, which appears
to be the case). Our criteria is not quite the same as other projects ...
basically you just need to be a committer in good standing in another Eclipse
Project, and affirm your commitment to contribute the bundle to the "Orbit
build" and be the "Orbit contact" for that third-party bundle.
So, if you are interested, just say so, and we'll begin the election process
right away.  And, of course, after you are a committer, we have some
"how to" wiki pages and can give advise and review as you get
started becoming an expert yourself! 

2) If you don't want to be a committer,
then you should open a bug in Orbit, stating the situation (that you'd
like it in Orbit but can not be a committer yourself). In that case, we'd
need an existing committer in Orbit to step forward to volunteer to contribute
it and be the contact (for example, perhaps someone else in Nebula is already
an Orbit committer? ... Or, heck, I'd almost volunteer myself, since NatTable
looks so cool! :) 

From there, either path, another CQ
would have to be open for Orbit (piggy-backed on your existing CQ) and
once approved (very quick and easy) then someone puts in in orbit's source
repo and build and then it becomes part of Orbit's p2 repository. 

I would like to clarify a few things
from your note, though: 

A)  you say, "we'd
like to have the bundle hosted in Orbit so that we can reference it in
our automated build". Technically,
you could have in your own build and repo and still reference it in your
automated build. The reason to put things in Orbit is 1) so it can be shared
more easily and consistently by other Eclipse Projects and 2) so the third
party jar benefits from the experts in Orbit that know how a lot about
how to make an ordinary jar usable by OSGi. There are a few rare cases
I know of where projects keep their third party code in their own repo
simply because they are positive no other project would want to use it
(e.g. it is old, and its required for some rare, fringe function). 

B) you say, "One
further complication is that the Apache POI jars don't have proper OSGi
manifests" ... that's not really
a complication ... that's (one of) the purposes of Orbit :) We add those
manifests (and a few other things) to nearly all the bundles in Orbit.
Only a few come to us a proper OSGi bundles. 

Thanks for your note. Let us know which
path you'd like to head down. 
 




From:      
 Edwin Park <esp1@xxxxxxxxxxx>
To:      
 orbit-dev <orbit-dev@xxxxxxxxxxx>,

Date:      
 08/09/2012 10:22 PM
Subject:    
   [orbit-dev]
Apache POI
Sent by:    
   orbit-dev-bounces@xxxxxxxxxxx

---

Hi,

I'd like to get Apache POI
included in Orbit. It has been approved for reuse in NatTable (http://www.eclipse.org/nattable, https://dev.eclipse.org/ipzilla/show_bug.cgi?id=6476),
but we'd like to have the bundle hosted in Orbit so that we can reference
it in our automated build. One further complication is that the Apache
POI jars don't have proper OSGi manifests, so they will need to be rewrapped
in order to be usable with OSGi. I haven't requested anything to be included
in Orbit before, so please let me know if you need any other info.

Thanks,
Edwin_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev