camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grzegorz Grzybek <gr.grzy...@gmail.com>
Subject Re: camel blueprint force usage of log4j
Date Mon, 19 Oct 2015 06:03:28 GMT
can you try:
mvn dependency:tree
?

regards
Grzegorz

2015-10-18 20:39 GMT+02:00 souciance <souciance.eqdam.rashti@gmail.com>:
> Hello Grzegorz
>
> It doesn't seem to work.
>
> After following your instructions and removing log4j and slf4j-logj412 and
> running the project it starts to download the log4j artifacts again.
>
>
> [INFO] --- camel-maven-plugin:2.15.1.redhat-620133:run (default-cli) @
> splitterjoin ---
> [INFO] Downloading:
> https://repository.apache.org/content/groups/public/log4j/log4j/1.2.17/log4j-1.2.17.pom
> [INFO] Downloaded:
> https://repository.apache.org/content/groups/public/log4j/log4j/1.2.17/log4j-1.2.17.pom
> (22 KB at 5.9 KB/sec)
> [INFO] Downloading:
> https://repository.apache.org/content/groups/public/org/slf4j/slf4j-log4j12/1.7.10/slf4j-log4j12-1.7.10.pom
>
>
> This is how my pom looks like:
>
>  <dependencies>
>     <dependency>
>       <groupId>org.apache.camel</groupId>
>       <artifactId>camel-core</artifactId>
>       <version>2.15.1.redhat-620133</version>
>        </dependency>
>     <dependency>
>       <groupId>org.apache.camel</groupId>
>       <artifactId>camel-blueprint</artifactId>
>       <version>2.15.1.redhat-620133</version>
>       </dependency>
>     <dependency>
>       <groupId>org.apache.camel</groupId>
>       <artifactId>camel-bindy</artifactId>
>       <version>2.15.1</version>
>     </dependency>
>     <dependency>
>       <groupId>org.apache.camel</groupId>
>       <artifactId>camel-test-blueprint</artifactId>
>       <version>2.15.1.redhat-620133</version>
>       <exclusions>
>         <exclusion>
>                 <artifactId>commons-logging</artifactId>
>                 <groupId>commons-logging</groupId>
>         </exclusion>
>       </exclusions>
>     </dependency>
>      <dependency>
>       <groupId>org.apache.camel</groupId>
>       <artifactId>camel-jaxb</artifactId>
>       <version>2.15.1.redhat-620133</version>
>     </dependency>
>     <dependency>
>     <groupId>org.apache.camel</groupId>
>     <artifactId>camel-freemarker</artifactId>
>     <version>2.15.1</version>
> </dependency>
>     <dependency>
>         <groupId>org.apache.camel</groupId>
>         <artifactId>camel-xstream</artifactId>
>         <version>2.15.1</version>
>         <type>bundle</type>
>     </dependency>
>     <dependency>
>         <groupId>com.thoughtworks.xstream</groupId>
>         <artifactId>xstream</artifactId>
>         <version>1.4.7</version>
>     </dependency>
>     <dependency>
>         <groupId>ch.qos.logback</groupId>
>         <artifactId>logback-classic</artifactId>
>         <version>1.1.3</version>
>     </dependency>
>     <dependency>
>         <groupId>ch.qos.logback</groupId>
>         <artifactId>logback-core</artifactId>
>         <version>1.1.3</version>
>     </dependency>
>     <dependency>
>         <groupId>org.slf4j</groupId>
>         <artifactId>jcl-over-slf4j</artifactId>
>         <version>1.7.5</version>
>     </dependency>
>   </dependencies>
>
> As you can see I have excluded commons-logging as well. Is there more
> needed? It does seem like blueprint indeed is directly dependent on log4j.
>
> /Souciance
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/camel-blueprint-force-usage-of-log4j-tp5772826p5772839.html
> Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message