How do I disable logging for a specific dependency in SBT?
up vote
8
down vote
favorite
I have the following build.sbt file:
version := "0.1"
scalaVersion := "2.10.0-RC1"
scalacOptions := Seq("-unchecked", "-deprecation", "-encoding", "utf8")
resolvers ++= Seq(
"sonatype releases" at "https://oss.sonatype.org/content/repositories/releases/",
"sonatype snapshots" at "https://oss.sonatype.org/content/repositories/snapshots/",
"typesafe repo" at "http://repo.typesafe.com/typesafe/releases/",
"spray repo" at "http://repo.spray.io/"
)
libraryDependencies ++= Seq(
"io.spray" % "spray-can" % "1.1-M4.2"
,"io.spray" % "spray-routing" % "1.1-M4.2"
,"io.spray" % "spray-testkit" % "1.1-M4.2"
,"io.spray" %% "spray-json" % "1.2.2" cross CrossVersion.full
,"com.typesafe.akka" %% "akka-actor" % "2.1.0-RC1" cross CrossVersion.full
,"org.specs2" %% "specs2" % "1.12.2" % "test" cross CrossVersion.full
,"com.typesafe" % "slick_2.10.0-RC1" % "0.11.2"
,"com.h2database" % "h2" % "1.3.166"
,"org.xerial" % "sqlite-jdbc" % "3.6.20"
,"org.slf4j" % "slf4j-api" % "1.6.4"
,"ch.qos.logback" % "logback-classic" % "1.0.7"
,"org.specs2" % "specs2_2.10.0-RC1" % "1.12.2" % "test"
,"junit" % "junit" % "4.8.1" % "test"
)
How do I enable DEBUG level reporting for my own (the current) project, but disable it for another. In this case I don't want to see the Slick library's debug output, but still want to see debug logging for my own project.
scala sbt slf4j logback slick
add a comment |
up vote
8
down vote
favorite
I have the following build.sbt file:
version := "0.1"
scalaVersion := "2.10.0-RC1"
scalacOptions := Seq("-unchecked", "-deprecation", "-encoding", "utf8")
resolvers ++= Seq(
"sonatype releases" at "https://oss.sonatype.org/content/repositories/releases/",
"sonatype snapshots" at "https://oss.sonatype.org/content/repositories/snapshots/",
"typesafe repo" at "http://repo.typesafe.com/typesafe/releases/",
"spray repo" at "http://repo.spray.io/"
)
libraryDependencies ++= Seq(
"io.spray" % "spray-can" % "1.1-M4.2"
,"io.spray" % "spray-routing" % "1.1-M4.2"
,"io.spray" % "spray-testkit" % "1.1-M4.2"
,"io.spray" %% "spray-json" % "1.2.2" cross CrossVersion.full
,"com.typesafe.akka" %% "akka-actor" % "2.1.0-RC1" cross CrossVersion.full
,"org.specs2" %% "specs2" % "1.12.2" % "test" cross CrossVersion.full
,"com.typesafe" % "slick_2.10.0-RC1" % "0.11.2"
,"com.h2database" % "h2" % "1.3.166"
,"org.xerial" % "sqlite-jdbc" % "3.6.20"
,"org.slf4j" % "slf4j-api" % "1.6.4"
,"ch.qos.logback" % "logback-classic" % "1.0.7"
,"org.specs2" % "specs2_2.10.0-RC1" % "1.12.2" % "test"
,"junit" % "junit" % "4.8.1" % "test"
)
How do I enable DEBUG level reporting for my own (the current) project, but disable it for another. In this case I don't want to see the Slick library's debug output, but still want to see debug logging for my own project.
scala sbt slf4j logback slick
In log4j.xml you can configure log level for each library.
– Rajesh Pitty
Nov 8 '12 at 10:13
add a comment |
up vote
8
down vote
favorite
up vote
8
down vote
favorite
I have the following build.sbt file:
version := "0.1"
scalaVersion := "2.10.0-RC1"
scalacOptions := Seq("-unchecked", "-deprecation", "-encoding", "utf8")
resolvers ++= Seq(
"sonatype releases" at "https://oss.sonatype.org/content/repositories/releases/",
"sonatype snapshots" at "https://oss.sonatype.org/content/repositories/snapshots/",
"typesafe repo" at "http://repo.typesafe.com/typesafe/releases/",
"spray repo" at "http://repo.spray.io/"
)
libraryDependencies ++= Seq(
"io.spray" % "spray-can" % "1.1-M4.2"
,"io.spray" % "spray-routing" % "1.1-M4.2"
,"io.spray" % "spray-testkit" % "1.1-M4.2"
,"io.spray" %% "spray-json" % "1.2.2" cross CrossVersion.full
,"com.typesafe.akka" %% "akka-actor" % "2.1.0-RC1" cross CrossVersion.full
,"org.specs2" %% "specs2" % "1.12.2" % "test" cross CrossVersion.full
,"com.typesafe" % "slick_2.10.0-RC1" % "0.11.2"
,"com.h2database" % "h2" % "1.3.166"
,"org.xerial" % "sqlite-jdbc" % "3.6.20"
,"org.slf4j" % "slf4j-api" % "1.6.4"
,"ch.qos.logback" % "logback-classic" % "1.0.7"
,"org.specs2" % "specs2_2.10.0-RC1" % "1.12.2" % "test"
,"junit" % "junit" % "4.8.1" % "test"
)
How do I enable DEBUG level reporting for my own (the current) project, but disable it for another. In this case I don't want to see the Slick library's debug output, but still want to see debug logging for my own project.
scala sbt slf4j logback slick
I have the following build.sbt file:
version := "0.1"
scalaVersion := "2.10.0-RC1"
scalacOptions := Seq("-unchecked", "-deprecation", "-encoding", "utf8")
resolvers ++= Seq(
"sonatype releases" at "https://oss.sonatype.org/content/repositories/releases/",
"sonatype snapshots" at "https://oss.sonatype.org/content/repositories/snapshots/",
"typesafe repo" at "http://repo.typesafe.com/typesafe/releases/",
"spray repo" at "http://repo.spray.io/"
)
libraryDependencies ++= Seq(
"io.spray" % "spray-can" % "1.1-M4.2"
,"io.spray" % "spray-routing" % "1.1-M4.2"
,"io.spray" % "spray-testkit" % "1.1-M4.2"
,"io.spray" %% "spray-json" % "1.2.2" cross CrossVersion.full
,"com.typesafe.akka" %% "akka-actor" % "2.1.0-RC1" cross CrossVersion.full
,"org.specs2" %% "specs2" % "1.12.2" % "test" cross CrossVersion.full
,"com.typesafe" % "slick_2.10.0-RC1" % "0.11.2"
,"com.h2database" % "h2" % "1.3.166"
,"org.xerial" % "sqlite-jdbc" % "3.6.20"
,"org.slf4j" % "slf4j-api" % "1.6.4"
,"ch.qos.logback" % "logback-classic" % "1.0.7"
,"org.specs2" % "specs2_2.10.0-RC1" % "1.12.2" % "test"
,"junit" % "junit" % "4.8.1" % "test"
)
How do I enable DEBUG level reporting for my own (the current) project, but disable it for another. In this case I don't want to see the Slick library's debug output, but still want to see debug logging for my own project.
scala sbt slf4j logback slick
scala sbt slf4j logback slick
asked Nov 8 '12 at 9:59
Jack
9,3891075146
9,3891075146
In log4j.xml you can configure log level for each library.
– Rajesh Pitty
Nov 8 '12 at 10:13
add a comment |
In log4j.xml you can configure log level for each library.
– Rajesh Pitty
Nov 8 '12 at 10:13
In log4j.xml you can configure log level for each library.
– Rajesh Pitty
Nov 8 '12 at 10:13
In log4j.xml you can configure log level for each library.
– Rajesh Pitty
Nov 8 '12 at 10:13
add a comment |
2 Answers
2
active
oldest
votes
up vote
5
down vote
accepted
In your logback.xml add an entry like this:
<logger name="com.typesafe.slick" level="INFO"/>
This means, that when a logger is obtained by any class of the namespace com.typesafe.slick
it will have INFO
set as log level.
edit: Here's the link to the documentation.
Cool thanks. I did that and it works. I was just hoping it was possible to keep course grained logging inclusions/exclusions as part of the SBT setup to avoid spreading settings in different files. For example, in SBT you set the runlevel e.g. test, or runtime, and in the same fashion it would have been nice to just tell it to set the log level for a library.
– Jack
Nov 8 '12 at 11:06
I don't think that is possible. Setting the log level is runtime configuration, but sbt can only affect compile time. Also you have to have a logback.xml anyway, so I don't see the benefit of adding more stuff to the build file.
– drexin
Nov 8 '12 at 11:12
I suppose it depends on the way you use SBT. It's not uncommon to set the name and location of the logback.xml file as part of SBT config, which can be used to achieve the desired effect. I was just hoping to simplify my setup a little.
– Jack
Nov 8 '12 at 11:44
4
It's worth noting that as of today (16/1/13) the correct name is "scala.slick", rather than "com.typesafe.slick"
– AlecZorab
Jan 16 '13 at 17:11
Following AlecZorab's comments the name is no longer 'scala.slick' but just 'slick'
– AlexC
Nov 12 '15 at 11:11
add a comment |
up vote
0
down vote
To see what name the logger of you dependency have you can use the standard logging appender in your logback.xml
. So if you have the following:
<configuration>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{HH:mm:ss} [%thread] %-5level %logger{1000} - %msg%n</pattern>
</encoder>
</appender>
<root level="info">
<appender-ref ref="STDOUT" />
</root>
</configuration>
You will get something like as a log message:
12:53:09 [AmexReporting-akka.stream.default-blocking-io-dispatcher-6]
INFO net.schmizz.sshj.connection.channel.direct.SessionChannel -
Will requestsftp
subsystem
Then you can add a logger between the appender and root level configuration:
<configuration>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{HH:mm:ss} [%thread] %-5level %logger{1000} - %msg%n</pattern>
</encoder>
</appender>
<logger name="net.schmizz.sshj" level="OFF"/>
<root level="info">
<appender-ref ref="STDOUT" />
</root>
</configuration>
Where the logger name is a part or the full package name that you can see in the log output, depending on how granular you want your log settings to be.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
accepted
In your logback.xml add an entry like this:
<logger name="com.typesafe.slick" level="INFO"/>
This means, that when a logger is obtained by any class of the namespace com.typesafe.slick
it will have INFO
set as log level.
edit: Here's the link to the documentation.
Cool thanks. I did that and it works. I was just hoping it was possible to keep course grained logging inclusions/exclusions as part of the SBT setup to avoid spreading settings in different files. For example, in SBT you set the runlevel e.g. test, or runtime, and in the same fashion it would have been nice to just tell it to set the log level for a library.
– Jack
Nov 8 '12 at 11:06
I don't think that is possible. Setting the log level is runtime configuration, but sbt can only affect compile time. Also you have to have a logback.xml anyway, so I don't see the benefit of adding more stuff to the build file.
– drexin
Nov 8 '12 at 11:12
I suppose it depends on the way you use SBT. It's not uncommon to set the name and location of the logback.xml file as part of SBT config, which can be used to achieve the desired effect. I was just hoping to simplify my setup a little.
– Jack
Nov 8 '12 at 11:44
4
It's worth noting that as of today (16/1/13) the correct name is "scala.slick", rather than "com.typesafe.slick"
– AlecZorab
Jan 16 '13 at 17:11
Following AlecZorab's comments the name is no longer 'scala.slick' but just 'slick'
– AlexC
Nov 12 '15 at 11:11
add a comment |
up vote
5
down vote
accepted
In your logback.xml add an entry like this:
<logger name="com.typesafe.slick" level="INFO"/>
This means, that when a logger is obtained by any class of the namespace com.typesafe.slick
it will have INFO
set as log level.
edit: Here's the link to the documentation.
Cool thanks. I did that and it works. I was just hoping it was possible to keep course grained logging inclusions/exclusions as part of the SBT setup to avoid spreading settings in different files. For example, in SBT you set the runlevel e.g. test, or runtime, and in the same fashion it would have been nice to just tell it to set the log level for a library.
– Jack
Nov 8 '12 at 11:06
I don't think that is possible. Setting the log level is runtime configuration, but sbt can only affect compile time. Also you have to have a logback.xml anyway, so I don't see the benefit of adding more stuff to the build file.
– drexin
Nov 8 '12 at 11:12
I suppose it depends on the way you use SBT. It's not uncommon to set the name and location of the logback.xml file as part of SBT config, which can be used to achieve the desired effect. I was just hoping to simplify my setup a little.
– Jack
Nov 8 '12 at 11:44
4
It's worth noting that as of today (16/1/13) the correct name is "scala.slick", rather than "com.typesafe.slick"
– AlecZorab
Jan 16 '13 at 17:11
Following AlecZorab's comments the name is no longer 'scala.slick' but just 'slick'
– AlexC
Nov 12 '15 at 11:11
add a comment |
up vote
5
down vote
accepted
up vote
5
down vote
accepted
In your logback.xml add an entry like this:
<logger name="com.typesafe.slick" level="INFO"/>
This means, that when a logger is obtained by any class of the namespace com.typesafe.slick
it will have INFO
set as log level.
edit: Here's the link to the documentation.
In your logback.xml add an entry like this:
<logger name="com.typesafe.slick" level="INFO"/>
This means, that when a logger is obtained by any class of the namespace com.typesafe.slick
it will have INFO
set as log level.
edit: Here's the link to the documentation.
answered Nov 8 '12 at 10:45
drexin
21.5k35675
21.5k35675
Cool thanks. I did that and it works. I was just hoping it was possible to keep course grained logging inclusions/exclusions as part of the SBT setup to avoid spreading settings in different files. For example, in SBT you set the runlevel e.g. test, or runtime, and in the same fashion it would have been nice to just tell it to set the log level for a library.
– Jack
Nov 8 '12 at 11:06
I don't think that is possible. Setting the log level is runtime configuration, but sbt can only affect compile time. Also you have to have a logback.xml anyway, so I don't see the benefit of adding more stuff to the build file.
– drexin
Nov 8 '12 at 11:12
I suppose it depends on the way you use SBT. It's not uncommon to set the name and location of the logback.xml file as part of SBT config, which can be used to achieve the desired effect. I was just hoping to simplify my setup a little.
– Jack
Nov 8 '12 at 11:44
4
It's worth noting that as of today (16/1/13) the correct name is "scala.slick", rather than "com.typesafe.slick"
– AlecZorab
Jan 16 '13 at 17:11
Following AlecZorab's comments the name is no longer 'scala.slick' but just 'slick'
– AlexC
Nov 12 '15 at 11:11
add a comment |
Cool thanks. I did that and it works. I was just hoping it was possible to keep course grained logging inclusions/exclusions as part of the SBT setup to avoid spreading settings in different files. For example, in SBT you set the runlevel e.g. test, or runtime, and in the same fashion it would have been nice to just tell it to set the log level for a library.
– Jack
Nov 8 '12 at 11:06
I don't think that is possible. Setting the log level is runtime configuration, but sbt can only affect compile time. Also you have to have a logback.xml anyway, so I don't see the benefit of adding more stuff to the build file.
– drexin
Nov 8 '12 at 11:12
I suppose it depends on the way you use SBT. It's not uncommon to set the name and location of the logback.xml file as part of SBT config, which can be used to achieve the desired effect. I was just hoping to simplify my setup a little.
– Jack
Nov 8 '12 at 11:44
4
It's worth noting that as of today (16/1/13) the correct name is "scala.slick", rather than "com.typesafe.slick"
– AlecZorab
Jan 16 '13 at 17:11
Following AlecZorab's comments the name is no longer 'scala.slick' but just 'slick'
– AlexC
Nov 12 '15 at 11:11
Cool thanks. I did that and it works. I was just hoping it was possible to keep course grained logging inclusions/exclusions as part of the SBT setup to avoid spreading settings in different files. For example, in SBT you set the runlevel e.g. test, or runtime, and in the same fashion it would have been nice to just tell it to set the log level for a library.
– Jack
Nov 8 '12 at 11:06
Cool thanks. I did that and it works. I was just hoping it was possible to keep course grained logging inclusions/exclusions as part of the SBT setup to avoid spreading settings in different files. For example, in SBT you set the runlevel e.g. test, or runtime, and in the same fashion it would have been nice to just tell it to set the log level for a library.
– Jack
Nov 8 '12 at 11:06
I don't think that is possible. Setting the log level is runtime configuration, but sbt can only affect compile time. Also you have to have a logback.xml anyway, so I don't see the benefit of adding more stuff to the build file.
– drexin
Nov 8 '12 at 11:12
I don't think that is possible. Setting the log level is runtime configuration, but sbt can only affect compile time. Also you have to have a logback.xml anyway, so I don't see the benefit of adding more stuff to the build file.
– drexin
Nov 8 '12 at 11:12
I suppose it depends on the way you use SBT. It's not uncommon to set the name and location of the logback.xml file as part of SBT config, which can be used to achieve the desired effect. I was just hoping to simplify my setup a little.
– Jack
Nov 8 '12 at 11:44
I suppose it depends on the way you use SBT. It's not uncommon to set the name and location of the logback.xml file as part of SBT config, which can be used to achieve the desired effect. I was just hoping to simplify my setup a little.
– Jack
Nov 8 '12 at 11:44
4
4
It's worth noting that as of today (16/1/13) the correct name is "scala.slick", rather than "com.typesafe.slick"
– AlecZorab
Jan 16 '13 at 17:11
It's worth noting that as of today (16/1/13) the correct name is "scala.slick", rather than "com.typesafe.slick"
– AlecZorab
Jan 16 '13 at 17:11
Following AlecZorab's comments the name is no longer 'scala.slick' but just 'slick'
– AlexC
Nov 12 '15 at 11:11
Following AlecZorab's comments the name is no longer 'scala.slick' but just 'slick'
– AlexC
Nov 12 '15 at 11:11
add a comment |
up vote
0
down vote
To see what name the logger of you dependency have you can use the standard logging appender in your logback.xml
. So if you have the following:
<configuration>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{HH:mm:ss} [%thread] %-5level %logger{1000} - %msg%n</pattern>
</encoder>
</appender>
<root level="info">
<appender-ref ref="STDOUT" />
</root>
</configuration>
You will get something like as a log message:
12:53:09 [AmexReporting-akka.stream.default-blocking-io-dispatcher-6]
INFO net.schmizz.sshj.connection.channel.direct.SessionChannel -
Will requestsftp
subsystem
Then you can add a logger between the appender and root level configuration:
<configuration>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{HH:mm:ss} [%thread] %-5level %logger{1000} - %msg%n</pattern>
</encoder>
</appender>
<logger name="net.schmizz.sshj" level="OFF"/>
<root level="info">
<appender-ref ref="STDOUT" />
</root>
</configuration>
Where the logger name is a part or the full package name that you can see in the log output, depending on how granular you want your log settings to be.
add a comment |
up vote
0
down vote
To see what name the logger of you dependency have you can use the standard logging appender in your logback.xml
. So if you have the following:
<configuration>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{HH:mm:ss} [%thread] %-5level %logger{1000} - %msg%n</pattern>
</encoder>
</appender>
<root level="info">
<appender-ref ref="STDOUT" />
</root>
</configuration>
You will get something like as a log message:
12:53:09 [AmexReporting-akka.stream.default-blocking-io-dispatcher-6]
INFO net.schmizz.sshj.connection.channel.direct.SessionChannel -
Will requestsftp
subsystem
Then you can add a logger between the appender and root level configuration:
<configuration>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{HH:mm:ss} [%thread] %-5level %logger{1000} - %msg%n</pattern>
</encoder>
</appender>
<logger name="net.schmizz.sshj" level="OFF"/>
<root level="info">
<appender-ref ref="STDOUT" />
</root>
</configuration>
Where the logger name is a part or the full package name that you can see in the log output, depending on how granular you want your log settings to be.
add a comment |
up vote
0
down vote
up vote
0
down vote
To see what name the logger of you dependency have you can use the standard logging appender in your logback.xml
. So if you have the following:
<configuration>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{HH:mm:ss} [%thread] %-5level %logger{1000} - %msg%n</pattern>
</encoder>
</appender>
<root level="info">
<appender-ref ref="STDOUT" />
</root>
</configuration>
You will get something like as a log message:
12:53:09 [AmexReporting-akka.stream.default-blocking-io-dispatcher-6]
INFO net.schmizz.sshj.connection.channel.direct.SessionChannel -
Will requestsftp
subsystem
Then you can add a logger between the appender and root level configuration:
<configuration>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{HH:mm:ss} [%thread] %-5level %logger{1000} - %msg%n</pattern>
</encoder>
</appender>
<logger name="net.schmizz.sshj" level="OFF"/>
<root level="info">
<appender-ref ref="STDOUT" />
</root>
</configuration>
Where the logger name is a part or the full package name that you can see in the log output, depending on how granular you want your log settings to be.
To see what name the logger of you dependency have you can use the standard logging appender in your logback.xml
. So if you have the following:
<configuration>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{HH:mm:ss} [%thread] %-5level %logger{1000} - %msg%n</pattern>
</encoder>
</appender>
<root level="info">
<appender-ref ref="STDOUT" />
</root>
</configuration>
You will get something like as a log message:
12:53:09 [AmexReporting-akka.stream.default-blocking-io-dispatcher-6]
INFO net.schmizz.sshj.connection.channel.direct.SessionChannel -
Will requestsftp
subsystem
Then you can add a logger between the appender and root level configuration:
<configuration>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{HH:mm:ss} [%thread] %-5level %logger{1000} - %msg%n</pattern>
</encoder>
</appender>
<logger name="net.schmizz.sshj" level="OFF"/>
<root level="info">
<appender-ref ref="STDOUT" />
</root>
</configuration>
Where the logger name is a part or the full package name that you can see in the log output, depending on how granular you want your log settings to be.
answered Nov 22 at 11:58
spydon
2,63141944
2,63141944
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f13286656%2fhow-do-i-disable-logging-for-a-specific-dependency-in-sbt%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
In log4j.xml you can configure log level for each library.
– Rajesh Pitty
Nov 8 '12 at 10:13