f61ecb65e7
In order to truely stay Java 8 compatible, declaring a source and target compatiblity is not sufficient. Source compatiblity means that the input, i.e. the code written in Java is compatible with that particular version of the Java Language Specification (JLS). And target compatibitliy means that the produced Java bytecode is compatible with that particular version of the Java Virtual Machine Specificiation (JVMS). But there is actually a third dimension: the runtime library (rt.jar). If signatures of methods change over java releases within the runtime library, then the produced bytecode, may contain calls to methods that do not exist with that exact same signature in older java versions. For example the family of Buffer subclasses changed the return value of certain functions, for example flip() to not return Buffer, but the concrete type of the current instance, e.g. CharBuffer. If we compile now with a newer JDK, where the return type is CharBuffer and not Buffer, then executing on an older JDK, where the return type is Buffer, then we get java.lang.NoSuchMethodError(s) thrown at us. Fixes SMACK-651. |
||
---|---|---|
.github | ||
config | ||
documentation | ||
resources | ||
smack-android | ||
smack-android-extensions | ||
smack-bosh | ||
smack-core | ||
smack-debug | ||
smack-debug-slf4j | ||
smack-experimental | ||
smack-extensions | ||
smack-im | ||
smack-integration-test | ||
smack-java7 | ||
smack-java8-full | ||
smack-jingle-old | ||
smack-legacy | ||
smack-omemo | ||
smack-omemo-signal | ||
smack-omemo-signal-integration-test | ||
smack-openpgp | ||
smack-repl | ||
smack-resolver-dnsjava | ||
smack-resolver-javax | ||
smack-resolver-minidns | ||
smack-resolver-minidns-dox | ||
smack-sasl-javax | ||
smack-sasl-provided | ||
smack-tcp | ||
smack-xmlparser | ||
smack-xmlparser-stax | ||
smack-xmlparser-xpp3 | ||
.gitignore | ||
.travis.yml | ||
build.gradle | ||
LICENSE | ||
README.md | ||
repl | ||
settings.gradle | ||
version.gradle |
Smack
About
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.
Getting started
Start with having a look at the Documentation and the Javadoc.
Instructions on how to use Smack in your Java or Android project are provided in the Smack Readme and Upgrade Guide.
Professional Services
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.
Bug Reporting
Only a few users have access for filling bugs in the tracker. New users should:
- Read "How to ask for help or report an issue"
- Create a discourse account (you can also sign up with your Google account).
- Login to the forum account
- Press "New Topic" in your toolbar and choose the 'Smack Support' sub-category.
Please search for your issues in the bug tracker before reporting.
Donate
If you find Smack useful and feel like donating, then you can use one of the following systems:
- Donate via Bitcoin: 1LiU78z3498wu3jwRPKbvovKAHjTcpVbuK
Contact
The developers hang around in #smack
(freenode, IRC) and open_chat@conference.igniterealtime.org
(XMPP MUC room).
Remember that it may take some time (~hours) to get a response.
You can also reach us via the Smack Support Forum if you have questions or need support, or the Smack Developers Forum if you want to discuss Smack development.
Contributing
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.
Resources
- Current Readme: https://igniterealtime.org/projects/smack/readme
- Bug Tracker: https://issues.igniterealtime.org/browse/SMACK
- JaCoCo Coverage Reports: https://www.igniterealtime.org/builds/smack/dailybuilds/jacoco/html/
- Nightly Javadoc: http://www.igniterealtime.org/builds/smack/dailybuilds/javadoc/
- Nightly Documentation: http://www.igniterealtime.org/builds/smack/dailybuilds/documentation/
- User Forum: https://discourse.igniterealtime.org/c/smack/smack-support
- Dev Forum: https://discourse.igniterealtime.org/c/smack/smack-dev
- Maven Releases: https://oss.sonatype.org/content/repositories/releases/org/igniterealtime/smack/
- Maven Snapshots: https://oss.sonatype.org/content/repositories/snapshots/org/igniterealtime/smack/
- Nightly Unique Maven Snapshots: https://igniterealtime.org/repo/
Ignite Realtime
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.
Smack - an Ignite Realtime community project.