Smack/smack-bosh/build.gradle

description = """\
Smack BOSH API.
This API is considered beta quality."""

dependencies {
	compile project(':smack-core')
	compile 'org.igniterealtime.jbosh:jbosh:(0.8,0.9]'
}
Move gradle subproject configuration into the subproject 2014-03-08 11:47:40 +01:00			`description = """\`
			`Smack BOSH API.`
			`This API is considered beta quality."""`

			`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')`
Use mathematical range syntax for dependencies In dd84d53bbc3f1868d06869f2f65e60a2c1976bc1 the usage of dynamic dependencies was removed because OSS Sonatype would not longer allow them, i.e. the '1.2.+' notation, on release artifacts. But they allow the mathematical range notation '(1.2,1.3]', therefore we use this now. 2014-12-17 16:23:24 +01:00			`compile 'org.igniterealtime.jbosh:jbosh:(0.8,0.9]'`
Move gradle subproject configuration into the subproject 2014-03-08 11:47:40 +01:00			`}`