| Re: [smila-dev] SMILA required libs in Orbit |
|
Check out the Orbit FAQ at
http://wiki.eclipse.org/index.php/Orbit_Faq. If there are questions
you have that it does not answer, don't hesitate to let the Orbit team
know. The whole point of Orbit is for the folks doing the bundling work to work together and share approach, advice, information, .... Bundling is largely the same from one project to the next so this should work. In the end you do the same thing you do now in SMILA but rather than doing it in the SMILA repo you do it in the Orbit repo. As for Sebastian's issues, please file an Orbit bug with fixes. The goal is to get one bundling of these libs that work for all and explicitly avoid the situation where, for example, the SMILA Xerces bundle has version numbers and the Orbit ones do not (or vice versa). Jeff August Georg Schmidt wrote: Hi Jeff, thanks for your request. As Sebastian mentioned we would like to use and contribute to Orbit. We currently do not yet know how the contribution process to Orbit will look alike. (Whether we do a reuse, or whether we just try to contribute our bundles if the "OSGi packaging quality" is higher or different. I think there may be interesting contributions that we could make for Orbit. Georg -----Original Message----- From: smila-dev-bounces@xxxxxxxxxxx [mailto:smila-dev-bounces@xxxxxxxxxxx] On Behalf Of Sebastian Voigt Sent: Donnerstag, 4. September 2008 10:02 To: Smila project developer mailing list Subject: RE: [smila-dev] SMILA required libs in Orbit Hi, our intention is to use and to contribute to orbit, but we have yet started to use the CQ-process and we are facing some problems, therefore we have to first to adapt some things. Regarding the Usage of Orbit-Bundles: We have tested some bundles with our trunk (that bundles that we need at the moment). The result is that we have problems with these bundles. Some Examples are: Some Bundles don't use version numbers for import/export (xalan/xerces) and commons logging can't be used with log4j. Then most of the bundles are too old, we have to build bundles for this and therefore we are working hard on CQs and on getting our project into svn. Until we have not finished this, we will not have time to contribute bundles to orbit. Sebastian-----Original Message----- From: smila-dev-bounces@xxxxxxxxxxx [mailto:smila-dev-bounces@xxxxxxxxxxx] On Behalf Of Jeff McAffer Sent: Tuesday, September 02, 2008 5:29 PM To: smila-dev@xxxxxxxxxxx Subject: [smila-dev] SMILA required libs in Orbit SMILA team I see a number of requests to reuse third party libs in SMILA. This is great. Do you have have plans to put these in Orbit as well? We are striving to combine the bundling efforts wrt third party libs under the Orbit project so that everyone in the community can help/share and so that ultimately we don't end up shipping largely diverse sets of versions. Your collaboration in this would greatly enhance this effort. Jeff _______________________________________________ smila-dev mailing list smila-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/smila-dev_______________________________________________ smila-dev mailing list smila-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/smila-dev _______________________________________________ smila-dev mailing list smila-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/smila-dev |