Smack/smack-im/build.gradle

description = """\
Smack IM.
Classes and methods for XMPP-IM (RFC 6121):
Roster, Chat and other functionality."""

// Note that the test dependencies (junit, …) are inferred from the
// sourceSet.test of the core subproject
dependencies {
	compile project(':smack-core')
	testCompile project(path: ":smack-core", configuration: "testRuntime")
}
Create smack-im subproject for XMPP-IM Move Roster and Chat(Manager) code into their own packages within the new smack-im subproject. Apply Manager pattern to Roster. Fixes SMACK-637. 2015-01-22 13:53:50 +01:00			`description = """\`
			`Smack IM.`
			`Classes and methods for XMPP-IM (RFC 6121):`
			`Roster, Chat and other functionality."""`

			`// Note that the test dependencies (junit, …) are inferred from the`
			`// sourceSet.test of the core subproject`
			`dependencies {`
			`compile project(':smack-core')`
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")`
Create smack-im subproject for XMPP-IM Move Roster and Chat(Manager) code into their own packages within the new smack-im subproject. Apply Manager pattern to Roster. Fixes SMACK-637. 2015-01-22 13:53:50 +01:00			`}`