Thanks Rajini
> There are two sets of classes that are shared across itest/osgi-tuscany and > the calculator subset. > > 1. OSGi installer - I did think of converting this into a module, but at > the moment, this is still experimental code, and we haven't really > decided > on what the final solution for a bundle-ized Tuscany will be. So > itest/osgi-tuscany felt like a better place for it. I think making this a module make sense even though it's not fully baked. It would at least remove this issue of duplicated code, i.e. we have one set of code in development rather than two sets. > 2. OSGi test harness - this runs samples (from the samples directory) in > an OSGi runtime. This is purely for testing, and doesn't really belong in > a > "module". If the calculator subset is turned into a sample, it should not > really use the harness since it is too complicated. If it is turned into > an > itest, it should be able to reuse the code directly from > itest/osgi-tuscany. > Sounds fair enough although we could make it a tool if you imagine that more than one itest would need to use it. > Simon > > > > > > -- > Thank you... > > Regards, > > Rajini >
