gemmellr commented on issue #2898: ARTEMIS-2557 doc caveat for OpenWire JMS 1.1 
   Personally I dont think this should really be documented, and would change 
the module config out such that the issue doesnt arise.
   The module has a transitive dep on the JMS 1.1 API via activemq-client, and 
has a transitive dep on the JMS 2.0 API via artemis-jms-client, and then 
further declares a non-transitive dep on JMS 1.1 itself. Various options likely 
exist to resolve the issue this doc update covers, stopping the 1.1 dep being 
passed to dependent componenents, while keeping things working for the 
module...e.g, excluding the transitive 1.1 dep from activemq-client, marking 
the fixed 1.1 dep as provided scope or optional, removing it entirely, 
declaring a fixed dep on JMS 2.0 spec, different combinations of these etc.
   I dont think using the JMS 2 API jar [,perhaps only at runtime,] for a 
server-side component of an otherwise JMS2-supporting broker really implies 
anything much about the spec level supported for clients, particularly as no 
client yet exists to follow through on any confusion that arises. Since the JMS 
2.0 API is still in the dep list here, if there is any scope for confusion it 
largely exists either way. Anyone that tries using JMS 2 APIs with a client 
that doesnt implement them will quickly find out it doesnt work, with it fairly 
simple to figure out why from the resulting errors. Anyone that really does 
want a 1.1 API + client used in something declaring a dep on 
artemis-openwire-protocol should already have their own dependency on them, in 
which case nothing would change by preventing the dep being passed on to them 
by artemis-openwire-protocol.

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:

With regards,
Apache Git Services

Reply via email to