From: Benjamin R. <br...@ya...> - 2007-12-10 15:57:01
|
An OSGi binding would be great. Yes, the OSGi jar should go into java/lib. I agree that the OSGi glue code should also be separate from the core code. Perhaps contrib/osgi/java. thanx ben On Saturday 08 December 2007 16:26:58 Alan D. Cabrera wrote: > On Dec 8, 2007, at 3:02 PM, Benjamin Reed wrote: > > I think for now we should focus on more near at hand problems until > > we run > > into issues with build. Currently Ant is more than adequate and we > > haven't > > had any issues yet. (I'm not saying we will not down the road, but > > it is > > better to pick a tool when you have a problem rather than risk > > picking the > > wrong tool before you've identified a problem.) > > I'm just going by my past experience in "both" worlds. It will be > tougher to convert than to do it at the outset but I'm not going to > push this further. No worries. > > I'd like to get this service bootable in an OSGi kernel for a start. > Here are some of my initial thoughts. I think that the OSGi code > should be separate from the "core" zoo code and so, probably, in a > different jar. Spring has some handy OSGi code but it's probably more > than we need at the moment. We'll need to compile against the OSGi > core jar. I'm guessing that goes in with the JUnit jar. > > Is there any more info that you'd like from me before I take a crack > at this? > > > Regards, > Alan > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Zookeeper-user mailing list > Zoo...@li... > https://lists.sourceforge.net/lists/listinfo/zookeeper-user |