Mercury-IM/Smack
Mercury-IM/Smack
1
0
Fork 0
mirror of https://codeberg.org/Mercury-IM/Smack synced 2024-10-31 22:15:59 +01:00
Code Issues Releases Wiki Activity
Smack/settings.gradle

18 lines
372 B
Groovy
Raw Normal View History

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
include 'smack-core',
'smack-tcp',
'smack-extensions',
'smack-experimental',
'smack-debug',
SLF4J Smack Debugging Logger
2014-08-15 13:28:07 +02:00
'smack-debug-slf4j',
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
'smack-resolver-dnsjava',
Add smack-resolver-minidns
2014-06-22 22:35:38 +02:00
'smack-resolver-minidns',
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
'smack-resolver-javax',
Add smack-android and redesign SASL authentication This commit marks an important milestone with the addition of the smack-android subproject. Smack is now able to run native on Android without requiring any modifications, which makes the aSmack build environment obsolete. It was necessary to redesign the code for SASL authentication to achieve this. Smack now comes with smack-sasl-provided for SASL implementations that do not rely on additional APIs like javax for platforms where those APIs are not available like Android.
2014-08-01 10:34:47 +02:00
'smack-sasl-javax',
'smack-sasl-provided',
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
'smack-compression-jzlib',
'smack-legacy',
Renamed smack-jingle to smack-jingle-old Also renamed package name from org.jivesoftware.smackx.jingle to org.jivesoftware.smackx.jingleold
2014-08-20 00:25:57 +02:00
'smack-jingle-old',
Add smack-java7
2014-07-20 12:58:36 +02:00
'smack-bosh',
Add smack-android and redesign SASL authentication This commit marks an important milestone with the addition of the smack-android subproject. Smack is now able to run native on Android without requiring any modifications, which makes the aSmack build environment obsolete. It was necessary to redesign the code for SASL authentication to achieve this. Smack now comes with smack-sasl-provided for SASL implementations that do not rely on additional APIs like javax for platforms where those APIs are not available like Android.
2014-08-01 10:34:47 +02:00
'smack-android',
'smack-java7'
Reference in a new issue Copy permalink