Smack/smack-experimental/build.gradle

description = """\
Smack experimental extensions.
Classes and methods for XEPs that are in status 'experimental' or that should
otherwise carefully considered for deployment. The API may change even
between patch versions."""

dependencies {
	compile project(':smack-core')
	compile project(':smack-extensions')
	testCompile project(path: ":smack-core", configuration: "testRuntime")
	testCompile project(path: ":smack-core", configuration: "archives")
	testCompile project(path: ":smack-extensions", configuration: "testRuntime")

	compile "org.bouncycastle:bcprov-jdk15on:$bouncyCastleVersion"
	compile "org.hsluv:hsluv:0.2"
}
Move gradle subproject configuration into the subproject 2014-03-08 11:47:40 +01:00			`description = """\`
			`Smack experimental extensions.`
			`Classes and methods for XEPs that are in status 'experimental' or that should`
			`otherwise carefully considered for deployment. The API may change even`
			`between patch versions."""`

			`dependencies {`
Prefix subprojects with 'smack-' instead of using the old baseName=smack appendix=project.name approach, we are now going convention over configuration and renaming the subprojects directories to the proper name. Having a prefix is actually very helpful, because the resulting libraries will be named like the subproject. And a core-4.0.0-rc1.jar is not as explicit about what it actually is as a smack-core-4.0.0-rc1.jar. SMACK-265 2014-04-28 19:27:53 +02:00			`compile project(':smack-core')`
			`compile project(':smack-extensions')`
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")`
			`testCompile project(path: ":smack-core", configuration: "archives")`
Improve MamTest - Use DummyConnection - Use InitExtensions 2017-02-24 19:32:46 +01:00			`testCompile project(path: ":smack-extensions", configuration: "testRuntime")`
Add Use of Cryptographic Hashfunctions (XEP-300) Also move bouncycastle dep from smack-omemo to smack-experimental. 2017-06-03 00:33:56 +02:00
Unify Bouncy Castle versions: Add bouncyCastleVersion variable 2019-04-02 15:53:47 +02:00			`compile "org.bouncycastle:bcprov-jdk15on:$bouncyCastleVersion"`
Update XEP-0392 to 0.6.0 2019-06-30 16:01:08 +02:00			`compile "org.hsluv:hsluv:0.2"`
Move gradle subproject configuration into the subproject 2014-03-08 11:47:40 +01:00			`}`