Has there been any plans to fine grain activemq-core based on optional dependencies.
-Separate library dedicated for a third party dependency would make it possible to have activemq-core in parent classloader relative to for instance activemq-spring. -Removal of now obsolete dependencies from activemq-core pom.xml would remove the need for explicit exclusions. -No more NoClassDefFoundErrors caused by missing optional dependencies This would ease out especially embedding which I found out to be quite a trial-and-error iteration process on already existing system which uses same dependencies as activemq-core. On the other hand overall complexity would be increased. -- View this message in context: http://www.nabble.com/Fine-graining-of-activemq-core-tp15353552s2354p15353552.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
