Smack/smack-debug-slf4j/build.gradle

description = """\
Smack slf4j debugger.
Inspect the exchanged XMPP stanzas.
Connect your favourite slf4j backend of choice to get output inside of it"""

dependencies {
    compile project(':smack-core')
    compile 'org.slf4j:slf4j-api:[1.7,1.8)'
    testCompile project(path: ":smack-core", configuration: "testRuntime")
}
SLF4J Smack Debugging Logger 2014-08-15 13:28:07 +02:00			`description = """\`
			`Smack slf4j debugger.`
			`Inspect the exchanged XMPP stanzas.`
			`Connect your favourite slf4j backend of choice to get output inside of it"""`

			`dependencies {`
			`compile project(':smack-core')`
Fix dependency version specification Mathematical range syntax was introduced with 31c53f094c9a613821b9e101f9d7f9bfd775b4e1, but unforutantely brackets and parentheses where reversed. 2015-02-19 14:28:46 +01:00			`compile 'org.slf4j:slf4j-api:[1.7,1.8)'`
Fix 'test' dependencies The previously used approach of project(':smack-core').sourceSets.test.runtimeClasspath caused the 'eclipse' target to produce duplicate classpath entries in .classpath when run with Gradle >= 2.6. It also relied on Gradle internals. Instead we now use project(path: ":smack-core", configuration: "testRuntime") project(path: ":smack-core", configuration: "archives") to be able to use test classes from other subprojects (usually smack-core) in e.g. smack-extensions. The 'archives' configuration includes the test jar. See also https://discuss.gradle.org/t/11784 Thanks to Lari Hotari for helping with this issue. 2016-02-10 12:39:18 +01:00			`testCompile project(path: ":smack-core", configuration: "testRuntime")`
SLF4J Smack Debugging Logger 2014-08-15 13:28:07 +02:00			`}`