[GitHub] qpid-jms issue #4: QPIDJMS-164: Provide OSGi metadata for qpid-jms-client
Github user gemmellr commented on the issue: https://github.com/apache/qpid-jms/pull/4 Thanks, merged. We likely won't use 1.X.Y etc versions until the AMQP JMS mapping the client is implementing, and the implementation in general, are a bit more settled. It only skipped a little to 0.20.0 to allow some leeway to do more releases while we are working on JMS 2 support, but there were no specific items in mind to actually do any though before now. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-jms issue #4: QPIDJMS-164: Provide OSGi metadata for qpid-jms-client
Github user ctron commented on the issue: https://github.com/apache/qpid-jms/pull/4 Ok. Done. I did change the title of the PR anyway, just as a note to myself. I also just saw that it actually targets javax.jms version 2. Is there a chance to get this change also for JMS version 1.1? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
