[GitHub] qpid-jms issue #20: Issue QPIDJMS-400: Add missing OSGI resolution:=optional...

2018-07-12 Thread Alex-Vol-SV
Github user Alex-Vol-SV commented on the issue: https://github.com/apache/qpid-jms/pull/20 I will try to manipulate the dependencies so that kqueue is the platform-neutral version. If that works I will close this pull request. ---

[GitHub] qpid-jms issue #20: Issue QPIDJMS-400: Add missing OSGI resolution:=optional...

2018-07-12 Thread gemmellr
Github user gemmellr commented on the issue: https://github.com/apache/qpid-jms/pull/20 That wont actually work since the epoll bits are required by default, as the classes are used by default, in determining whether the functionality is currently available. ---

[GitHub] qpid-jms issue #20: Issue QPIDJMS-400: Add missing OSGI resolution:=optional...

2018-07-12 Thread Alex-Vol-SV
Github user Alex-Vol-SV commented on the issue: https://github.com/apache/qpid-jms/pull/20 I will try that but IMHO using "optional" is the right approach. Lets the OSGI dependency system do the right thing automatically without forcing developers to play games with the dependency

[GitHub] qpid-jms issue #20: Issue QPIDJMS-400: Add missing OSGI resolution:=optional...

2018-07-12 Thread gemmellr
Github user gemmellr commented on the issue: https://github.com/apache/qpid-jms/pull/20 > FYI, attempting to exclude the transitive dependency on the kqueue jar so only the epoll jar is available in the bundle does not fix the problem, the OSGI container again complains about the

[GitHub] qpid-jms issue #20: Issue QPIDJMS-400: Add missing OSGI resolution:=optional...

2018-07-12 Thread Alex-Vol-SV
Github user Alex-Vol-SV commented on the issue: https://github.com/apache/qpid-jms/pull/20 We are using the qpid-jms client as the primary dependency in a Felix container. The change fixed the activation issue for what its worth. The "Optional" flag does not mean the activation does

[GitHub] qpid-jms issue #20: Issue QPIDJMS-400: Add missing OSGI resolution:=optional...

2018-07-12 Thread gemmellr
Github user gemmellr commented on the issue: https://github.com/apache/qpid-jms/pull/20 I agree the Travis CI OSX failure is unrelated. There isn't a way to trigger a new build on the github mirror without updating the PR. I don't think this change is actually quite the way

[GitHub] qpid-jms issue #20: Issue QPIDJMS-400: Add missing OSGI resolution:=optional...

2018-07-03 Thread Alex-Vol-SV
Github user Alex-Vol-SV commented on the issue: https://github.com/apache/qpid-jms/pull/20 The failure in the Travis CI seems unrelated to my changes. I did not have a failure when building this on Ubuntu with Java 8. Should I try the same on MacOS? I have access to a Mac with XCode