Hi Yeah we should exclude that old c3p0, it was a mistake in the git commit that forgot doing this: d1c7f65079ef94fd27a735d9c02e38920975dfa6
On Fri, Jul 8, 2016 at 3:31 PM, habdank <habd...@gmail.com> wrote: > Dears, > > I am not sure what is really right, but my maven build complains that c3p0 > classes are overlapping. > > Below there is copy of the dependency:tree and I see indeed that one time > c3p0 are in version 0.9.1.1 and the other just close to it 0.9.5.2. > > [INFO] +- org.apache.camel:camel-quartz2:jar:2.17.1:compile > [INFO] | +- org.quartz-scheduler:quartz:jar:2.2.2:compile > [INFO] | | \- c3p0:c3p0:jar:0.9.1.1:compile > [INFO] | \- com.mchange:c3p0:jar:0.9.5.2:compile > [INFO] | \- com.mchange:mchange-commons-java:jar:0.2.11:compile > > Is that expected? What shall I do to avoid maven complains? > > Best regards, > Seweryn. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Conflicting-c3p0-versions-tp5784962.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
