Hi I've no actual OSGi experience, but from watching various OSGi discussions, and playing with Eclipse, the minimum Pivot should provide is an OSGi-manifest that specifies the "actual public" classes, as opposed to the "public because it has to be, but actually internal" classes.
Also, there would be (1) the matter of maintaining the Pivot version number in the OSGi-manifest. (2) any inter-jar dependencies should also be in the manifest, with the requisite care about specifying optional vs. required dependencies. (3) perhaps adding the eclipse-specific metadata that specifies the minimum required Java environment. That would not necessarily be a complete implementation of OSGi-fication, but it would make the life of someone who wanted to drop Pivot into an OSGi container much easier. Regards, Noel. Greg Brown wrote: > Hi all, > > There was a thread a couple weeks ago about making the Pivot JARs > OSGi-compliant: > > http://mail-archives.apache.org/mod_mbox/incubator-pivot-dev/200907.mbox/%[email protected]%3e > > > This seems like a good idea, but it sounds like there may be some > challenges. Chris, you seem to have the most experience with OSGi - is > this something you would be willing to look into? Obviously, the first > step would simply be assessing the effort required. Then, depending on > the level of effort/timeframe, we could decide whether or not we want > to proceed. > > What do you think? > > Thanks, > Greg >
