AeroGear's Android libraries were built as jar and aar packages using Maven and the android-maven-plugin. The project follows the standard Maven layout so it can be imported directly into most IDEs as a Maven project.
AeroGear for Android provides support for integrating with push. Currently only using Google’s Cloud Messaging (GCM) with the AeroGear UnifiedPush Server is supported, but we are planning to add support for Mozilla’s Simple Push, MQTT, and standalone GCM soon.
| Project Info | |
|---|---|
| License: | Apache License, Version 2.0 |
| Build: | Maven |
| Documentation: | http://aerogear.org/docs/guides/aerogear-android/ |
| Issue tracker: | https://issues.jboss.org/browse/AGDROID |
| Mailing lists: | aerogear-users (subscribe) |
| aerogear-dev (subscribe) |
Please take a look at the step by step guide on our website.
The following dependencies are required to build this project:
There are two supported ways of developing apps using AeroGear for Android: Android Studio and Maven.
Add to your application's build.gradle file
dependencies {
compile 'com.google.android.gms:play-services:+'
compile 'org.jboss.aerogear:aerogear-android-core:2.0.0'
compile 'org.jboss.aerogear:aerogear-android-push:2.0.0'
}
Include the following dependencies in your project's pom.xml
<dependency>
<groupId>org.jboss.aerogear</groupId>
<artifactId>aerogear-android-push</artifactId>
<version>2.0.0</version>
<scope>provided</scope>
<type>jar</type>
</dependency>
<dependency>
<groupId>org.jboss.aerogear</groupId>
<artifactId>aerogear-android-push</artifactId>
<version>2.0.0</version>
<type>aar</type>
</dependency>
For more details about the current release, please consult our documentation.
Take a look in our demo apps
If you would like to help develop AeroGear you can join our developer's mailing list, join #aerogear on Freenode, or shout at us on Twitter @aerogears.
Also takes some time and skim the contributor guide
Join our user mailing list for any questions or help! We really hope you enjoy app development with AeroGear!
If you found a bug please create a ticket for us on Jira with some steps to reproduce it.