mirror of
https://codeberg.org/Mercury-IM/Smack
synced 2024-12-01 18:52:08 +01:00
529e1eb058
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.
15 lines
602 B
Groovy
15 lines
602 B
Groovy
description = """\
|
|
Smack extensions.
|
|
Classes and methods that implement support for the various XMPP XEPs
|
|
(Multi-User Chat, PubSub, …) and other XMPP extensions."""
|
|
|
|
// Note that the test dependencies (junit, …) are inferred from the
|
|
// sourceSet.test of the core subproject
|
|
dependencies {
|
|
compile project(':smack-core')
|
|
// Some implementations need APIs provided by smack-im,
|
|
// e.g. message delivery receipts the roster
|
|
compile project(':smack-im')
|
|
testCompile project(path: ":smack-core", configuration: "testRuntime")
|
|
testCompile project(path: ":smack-core", configuration: "archives")
|
|
}
|