mattrpav commented on PR #1738:
URL: https://github.com/apache/activemq/pull/1738#issuecomment-4060827995

   > but it's one class for now so splitting now just makes it harder for us.
   
   I think this line of thinking 'it's just one class' is what gets us into 
dependency trouble as a project. Yes, it is one class in the ActiveMQ tree, but 
this pulls in several transitive dependencies-- not just the one listed as 
optional.
   
   I think it would be most correct to have separate modules per security 
mechanism (the shiro appoarch). We could do an activemq-jaas-extras, but that 
doesn't seem to make sense b/c rarely are multiple external security providers 
(used outside of local accounts).
   
   
   
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact


Reply via email to