-
Notifications
You must be signed in to change notification settings - Fork 549
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IoT has prerelease dependency #145
Comments
It looks to me like upstream development is moving to eclipse/paho.mqtt.android (contrast, @jpwsutton Do I understand the split correctly? |
Hi, that's right, we've split out the Android service from the Java Repository. However the 1.0.3-SNAPSHOT will be promoted to our 1.1.0 release sometime in the next few days. Once that has happened, It will be available in Maven Central like the current 1.0.2 service (http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22org.eclipse.paho.android.service%22) That will mean that you won't have to add the eclipse snapshots repo. Of course if you want to continue using our snapshot builds, then you will have to add it (Maven central doesn't host snapshots). |
Thanks for the clarification! |
@mockturtl AWS SDK for Android v2.2.21 updates Paho MQTT client to 1.1.0. It may take up to a day before jCenter catching up with Maven central. Consumers can take the latest version without adding the snapshot repo. |
Consuming projects will not build.
As of 2.2.16,
aws-android-sdk-iot
depends onorg.eclipse.paho.client.mqttv3:1.0.3-SNAPSHOT
.@797c0df | changelog
Workaround: consumers can use 2.2.15, or add the upstream Paho snapshot repo. (example)
The text was updated successfully, but these errors were encountered: