On Fri, Mar 22, 2013 at 7:00 PM, kishore g <[email protected]> wrote: > > So we really dont know what it takes to make Helix OSGi > ready. Is this something you can drive, of course we can help you where > ever needed. >
Yes. > I am also assuming that we will have a separate helix-OSGi module within > Helix and thats the only module that might bring in additional dependency > jars from OSGi. I prefer Helix-core to be light weight and not add > additional dependency. Also making Helix OSGi ready does not mean thats the > only way to deploy it. Well, the first step is to make sure that the helix jars provide proper OSGi metadata. No dependencies needed here. At some point we might need to leverage OSGi services (though not sure if this will be required, yet). Using services would require a "provided" dependency on the osgi core. If you are relluctant about adding a dependency even as "provided", then we can create a separate module for hosting them. I'll create a jira. -- *Ioannis Canellos* * ** Blog: http://iocanel.blogspot.com ** Twitter: iocanel *
