brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hadrian Zbarcea <>
Subject Re: [PROPOSAL] Split brooklyn-core during OSGification
Date Mon, 12 Oct 2015 15:59:34 GMT
I think we'll need to split the core in multiple parts actually. I am 
having a bit of trouble myself with winrm4j. The complication is that it 
depends on jython, which does not provide an OSGi bundle either. I am 
not sure for instance if winrm4j is always necessary or it could be 
another core-ish bundle.

A second thought is that I don't know what the impact on current users 
would be to move the current use of the OSGi framework in a different 
jar. One possibility is to split the core into multiple jar, following a 
convention we can agree upon (brooklyn-rt-* would be a common 
convention), but then let what Cipi called brooklyn-rt-felix, keep the 
current name brooklyn-core.


On 10/12/2015 09:53 AM, Ciprian Ciubotariu wrote:
> While working on running Brooklyn inside Karaf I ran into the code that
> manages an embedded Apache Felix runtime.
> Since the roles are now reversed, I propose to split brooklyn-core into the
> following:
> * brooklyn-core - new implementation using the Karaf-provided OSGi runtime
> * brooklyn-rt-felix - existing code using felix as an embedded OSGI runtime
> (which will no longer be needed when OSGification is complete)
> This change is much needed since the Apache Felix packages that are used to
> start and stop the embedded framework are private within the felix bundle
> My intention is to move current code to brooklyn-rt-felix, and defer to it
> when the Karaf container is not present, while using the Karaf-provided
> felix/equinox framework by default.
> I have already started to code in that direction, but since this is a larger
> change I would like to hear your thoughts on the matter.

View raw message