Damn, was too late checking this in. The only issue with quartz-openejb-shade was trying to use the quartz version rather than 'omitting' the version so that it resolves to the parent project version (i.e. 4.6.1-SNAPSHOT) - This is how it should be, as we really want to keep control of the shade at build time when we deploy to either a snapshot or release repo.
Moving it out of the project completely is IMHO not the way to go as it complicates the build/deploy and release even more. Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/Quartz-next-tp4666498p4666649.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
