The logging should be on test scope if anything as running on karaf has its own osgi logging ,and you should not have those at compile scope.
I guess its because you may run it outside osgi from a camel main or something. Then you need to change the scopes if you want to see logging there. On Mon, Nov 7, 2016 at 11:17 AM, souciance <souciance.eqdam.ras...@gmail.com> wrote: > Hello, > > I did not have this issue with Camel blueprint archetype 2.15.0 but in > 2.17.0 it has appeared. I simply create a new project in intellij based on > camel-blueprint archetype for version 2.17.0. > > Everything is created but when running the project it gives me the error: > > [INFO] --- camel-maven-plugin:2.17.0:run (default-cli) @ email-bibsent --- > [INFO] camel-blueprint detected on classpath > [INFO] OSGi Blueprint XML files detected in directory > C:\Work\repo\LSP\integration-platform\integrations\PollEmailFromBibsent\src\main\resources\OSGI-INF\blueprint > [INFO] Using org.apache.camel.test.blueprint.Main to initiate a CamelContext > [INFO] Starting Camel ... > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further > details. > > Afterwards I have to change the dependency to add slf4j-simple. Is this the > correct procedure? > > > <dependency> > <groupId>org.slf4j</groupId> > <artifactId>slf4j-api</artifactId> > <version>${slf4j-version}</version> > </dependency> > <dependency> > <groupId>org.slf4j</groupId> > <artifactId>slf4j-simple</artifactId> > <version>${slf4j-version}</version> > </dependency> > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-archetype-2-17-0-onwards-tp5789819.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
