@cclamb since you have done some leg work on figuring out what is broken would it be possible for you to research a solution for this? I have not touched OSGi since pre-2 spec days and we have no resident OSGi person as a committer.

Sure, I'll see what I can do. I'm kinda an OSGi newbie, I'm having to use
in on a project I'm enaged with, but I understand that even my smidgen of
experience might make be the best suited for the job :)

I'm a bit swamped right now, but should be able to take a look in a few
weeks?

On Mon, Mar 18, 2013 at 9:53 AM, Thomas E Enebo notifications@github.comwrote:

@cclamb https://github.com/cclamb since you have done some leg work on
figuring out what is broken would it be possible for you to research a
solution for this? I have not touched OSGi since pre-2 spec days and we
have no resident OSGi person as a committer.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/589#issuecomment-15062778
.

Just FYI -- Saw this in v1.7.4, though I don't see it now in 1.7.10 so a fix for it likely snuck in within the .4-.10 maintenance releases.

Sounds good - we ended up working around via a different OSGi
implementation.

On Fri, Feb 7, 2014 at 6:49 PM, dabdine notifications@github.com wrote:

Just FYI -- Saw this in v1.7.4, though I don't see it now in 1.7.10 so a
fix for it likely snuck in within the .4-.10 maintenance releases.

Reply to this email directly or view it on GitHubhttps://github.com//issues/589#issuecomment-34524978
.