[GitHub] [activemq] mattrpav commented on pull request #682: [AMQ-7309] Update to jakarta.jms/jakarta.jms-api:2.0.3

[GitBox <gi...@apache.org>]

mattrpav commented on pull request #682:
URL: https://github.com/apache/activemq/pull/682#issuecomment-881557987


   @jbonofre this change is purely packaging skeleton. I know you were working on full JMS 2.0 support along w/ big things like replicated-kahadb. I thought I'd pitch in to help get the ball rolling on the low-hanging fruit. There is no real code change here, so I think its good to merge and should slide in with your real JMS 2.0 impl work.
   
   Reviewing other projects and frameworks, I think the geronimo vs jakarta is the real question here. 
   
   If we go geronimo users will have this to look forward to:
   gerinomo 1.1 -> geronimo 2.0 -> jakarta 2.0 -> jakarta 3.0
   
   Alternatively, if we go jakarta now, users have this:
   gerinomo 1.1 -> jakarta 2.0 -> jakarta 3.0
   
   CXF has transitioned many spec jars to jakarta, and I suspect Camel will do the same as well. I think the alignment makes more sense for CXF and Camel to consume the dep ActiveMQ (being as ActiveMQ is the JMS provider and those ride on top of), or simply provide the <exclude/>.
   
   Either way, the JEE transition is going to force users into being savvy with Maven <exclude/> and I do not think there is any way around that.
   
   I'd be interested in hearing others' perspective as well.


-- 
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.

To unsubscribe, e-mail: gitbox-unsubscribe@activemq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org