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(':smack-core').sourceSets.test.runtimeClasspath
}
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')`
			`testCompile project(':smack-core').sourceSets.test.runtimeClasspath`
Move gradle subproject configuration into the subproject 2014-03-08 11:47:40 +01:00			`}`