rmannibucau commented on pull request #37: URL: https://github.com/apache/openjpa/pull/37#issuecomment-700943541
> Again, by staying with the JMS 1.1 requirement, we are limiting JMS providers, and making it more difficult to integrate OpenJPA with other projects. For example, recent versions of Camel ship with JMS v2.0 jar dependencies. If we force OpenJPA to stay with 1.1, we will never get a valid wiring for a project that depends on Camel+OpenJPA. This is wrong, osgi knows that v1 works with v2, this is how all specs are done btw. The issue is the range as mzntionned which is not the dependency but explicit manual value as writtzn previously. Once again, i agree we should fix the range but we shouldnt upgrade the dependency as explained. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
