[
https://issues.apache.org/jira/browse/AMQ-7309?focusedWorklogId=623712&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-623712
]
ASF GitHub Bot logged work on AMQ-7309:
---------------------------------------
Author: ASF GitHub Bot
Created on: 16/Jul/21 16:13
Start Date: 16/Jul/21 16:13
Worklog Time Spent: 10m
Work Description: mattrpav edited a comment on pull request #682:
URL: https://github.com/apache/activemq/pull/682#issuecomment-881557987
@jbonofre this change is purely packaging skeleton. I know you mentioned
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 this PR good to merge and should
slide in with your real JMS 2.0 impl work. I also broke up the 2.0 Impl work
into sub-tasks here-- https://issues.apache.org/jira/browse/AMQ-7309. This
should help parallelize the effort amongst contributors.
Reviewing other projects and frameworks, I agree the geronimo vs jakarta is
the real question here and I think it makes more sense to go to the Jakarta jar
now as it is more target state than using geronimo.
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 as those ride
on top of ActiveMQ), or they simply provide the <exclude/>. Either way, the JEE
transition is going to force framework devs and 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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 623712)
Time Spent: 50m (was: 40m)
> Add JMS 2.0 support
> -------------------
>
> Key: AMQ-7309
> URL: https://issues.apache.org/jira/browse/AMQ-7309
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker, JMS client
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 5.17.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
