On 10/12/2015 12:18 PM, Aled Sage wrote:
Makes sense splitting up the core. +1 to moving winrm-integration. I'd be happy to make that an optional dependency, rather than it always being pulled in. But I'm keen that we don't break Windows support, so that it can still (somehow) be included. *Alex*, are you saying they want to exclude it because of its size? Or some other reason? --- *Hadrian*, For the impact to current users, are you thinking in terms of renaming bundles and/or packages that are being referenced by users' OSGi manifests? Or something else?
No, I meant keeping the name of the jar unchanged.
If it "just" requires users to update their manifests slightly and rebuild their bundles, then I think that is acceptable.
Yeah, would only require fixing the names in the dependencies and rebuild.
--- *Hadrian*, It feels like brooklyn-rt-felix should have just the felix-specific code (rather than it being a rename of the current brooklyn-core). I'm not sure I follow that suggestion.
Never mind, just trying to reduce the totally minor impact of renaming.
--- I'd also take the split-up opportunity to move the task framework to its own bundle, but that is low priority.
Let's create an issue for this in JIRA for tracking. Hadrian
