Changes: Rework integration tests New structure of base integration test classes bump dependency on signal-protocol-java from 2.4.0 to 2.6.2 Introduced CachingOmemoStore implementations Use CachingOmemoStore classes in integration tests Removed OmemoSession classes (replaced with more logical OmemoRatchet classes) Consequently also removed load/storeOmemoSession methods from OmemoStore Removed some clutter from KeyUtil classes Moved trust decision related code from OmemoStore to TrustCallback Require authenticated connection for many functions Add async initialization function in OmemoStore Refactor omemo test package (/java/org/jivesoftware/smack/omemo -> /java/org/jivesoftware/smackx) Remove OmemoStore method isFreshInstallation() as well as defaultDeviceId related stuff FileBasedOmemoStore: Add cleaner methods to store/load base data types (Using tryWithResource, only for future releases, once Android API gets bumped) Attempt to make OmemoManager thread safe new logic for getInstanceFor() deviceId determination OmemoManagers encrypt methods now don't throw exceptions when encryption for some devices fails. Instead message gets encrypted when possible and more information about failures gets returned alongside the message itself Added OmemoMessage class for that purpose Reworked entire OmemoService class Use safer logic for creating trust-ignoring messages (like ratchet-update messages) Restructure elements/provider in order to prepare for OMEMO namespace bumps Remove OmemoManager.regenerate() methods in favor of getInstanceFor(connection, randomDeviceId) Removed some unnecessary configuration options Prepare for support of more AES message key types Simplify session creation Where possible, avoid side effects in methods Add UntrustedOmemoIdentityException Add TrustState enum More improved tests
|2 years ago|
|config||2 years ago|
|documentation||2 years ago|
|resources||2 years ago|
|smack-android||2 years ago|
|smack-android-extensions||2 years ago|
|smack-bosh||2 years ago|
|smack-compression-jzlib||2 years ago|
|smack-core||2 years ago|
|smack-debug||2 years ago|
|smack-debug-slf4j||2 years ago|
|smack-experimental||2 years ago|
|smack-extensions||2 years ago|
|smack-im||2 years ago|
|smack-integration-test||2 years ago|
|smack-java7||2 years ago|
|smack-jingle-old||2 years ago|
|smack-legacy||2 years ago|
|smack-omemo||2 years ago|
|smack-omemo-signal||2 years ago|
|smack-omemo-signal-integration-test||3 years ago|
|smack-repl||2 years ago|
|smack-resolver-dnsjava||2 years ago|
|smack-resolver-javax||2 years ago|
|smack-resolver-minidns||2 years ago|
|smack-sasl-javax||2 years ago|
|smack-sasl-provided||2 years ago|
|smack-tcp||2 years ago|
|.gitignore||3 years ago|
|.travis.yml||2 years ago|
|LICENSE||3 years ago|
|README.md||2 years ago|
|build.gradle||2 years ago|
|repl||2 years ago|
|settings.gradle||3 years ago|
|version.gradle||2 years ago|
Smack is an open source, highly modular, easy to use, XMPP client library written in Java for Java SE compatible JVMs and Android.
A pure Java library, it can be embedded into your applications to create anything from a full XMPP instant messaging client to simple XMPP integrations such as sending notification messages and presence-enabling devices. Smack and XMPP allows you to easily exchange data, in various ways e.g. fire-and-forget, publish-subscribe, between human and non-human endpoints (M2M, IoT, …).
More information are provided by the Overview.
Instructions how to use Smack in your Java or Android project are provided in the Smack 4.2 Readme and Upgrade Guide.
Smack is a collaborative effort of many open source, professionally and spare-time, paid and unpaid, contributors. While we try to provide the best possible XMPP library for Android and Java SE compatible execution environments by following state of the art software engineering practices, the API may not always perfectly fit your requirements. We welcome contributions and encourage discussion about how Smack can be further improved. We also provide paid services ranging from XMPP/Smack related consulting to designing and developing features in order to accommodate your needs. Please contact Florian Schmaus for further information.
Only a few users have access for filling bugs in the tracker. New users should:
Please search for your issues in the bug tracker before reporting.
If you find Smack useful and feel like donating, then you can use one of the following systems:
The developers hang around in
#smack (freenode, IRC) and
email@example.com (XMPP MUC room).
Remember that it may take some time (~hours) to get a response.
If you want to start developing for Smack and eventually contribute code back, then please have a look at the Guidelines for Smack Developers and Contributors. The guidelines also contain development quickstart instructions.
Ignite Realtime is an Open Source community composed of end-users and developers around the world who are interested in applying innovative, open-standards-based RealTime Collaboration to their businesses and organizations. We're aimed at disrupting proprietary, non-open standards-based systems and invite you to participate in what's already one of the biggest and most active Open Source communities.