On Thu, May 15, 2008 at 2:59 AM, Jean-Sebastien Delfino < [EMAIL PROTECTED]> wrote:
> Graham Charters wrote: > >> Hi, >> >> I've been working on a small sample to act as an OSGi "sniff test" for >> Tuscany running in OSGi. It's basically a cut-down version of what >> Rajini has done in itest/osgi-tuscany and only runs the most basic >> Calculator sample. I still have some work to do to exclude all the >> things which aren't required and also perhaps move it to use the >> latest "1 manifest per 3rd party jar" approach. >> >> Currently the sample takes ~3 mins to build and run and uses 56MB. >> The main space usage is 17.5MB for the third-party dependencies and >> 35MB for the Felix bundle cache (61 bundles in total). The full >> Tuscany (itest/osgi-tuscany) using the same third-party library >> approach is 151 bundles and 133MB total. >> >> I'd like to understand whether people feel this would be useful >> > > Yes it's useful IMO > > and > >> whether it is approaching the kind of overhead that would be >> acceptable for it to be included in the main build? >> > > +1 from me to include it in the main build (assuming you meant main build = > top-down build from java/sca with profile "default") > > I'm +1 too to integrate the bigger itest/osgi-tuscany under another "osgi" > profile. > > Thoughts? > > >> Regards, Graham. >> > > > -- > Jean-Sebastien > Nice work Graham +1 from me to include this cut down sample in the main build. It's a great benchmark for how small we can get the minimum runtime and, for the subset that it represents, demonstrates that our OSGi support is working. I'm sure that you are right that we can cut it down further but that shouldn't prevent us getting it into the build. Simon
