Hi Grzegorz, I do not have direct dependency to: org.quartz-scheduler:quartz
I have only: <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-quartz2</artifactId> <version>2.17</version> <dependency> And conflict is created internally in camel-quartz2, this pom is not really mine. I can of course exclude c3p0 in camel-quartz2, and add it explicit on top of the camel-quartz2, but this solution is pretty odd, because in fact the version of the c3p0 is ruled by camel-quartz2 and not my project. Best regards, Seweryn. -- View this message in context: http://camel.465427.n5.nabble.com/Conflicting-c3p0-versions-tp5784962p5784964.html Sent from the Camel - Users mailing list archive at Nabble.com.