Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] Splitting Java and Android
Hi James,

I had the idea before to split the Android and Java code and think it would definitely help maintaining, reading and understanding the code. 

Do I understand you correct that you would like to to include/ bundle a specific version of the MqttClient into the Android service? Yes I thing that is possible and if someone wants to test with a newer or old version they still could use

compule('org.eclipse.paho:org.eclipse.paho.android.service:1.0.2') {
    exclude module: 'org.eclipse.paho.client.mqttv3'
}
and then supply there own version of the mqttv3 client. 

Keep up the good work,
Sandro


Am 22.02.2016 um 11:25 schrieb James Sutton1 <james.sutton@xxxxxxxxxx>:

Hi Everyone,
 
One of the last major pieces of work to happen to the Paho Android service was to move it from the legacy Maven / Eclipse build & IDE to the newer Gradle / Android Studio format. This went well and actually helped surface a few bugs / issues that existed in the codebase and also helped me upgrade the sample app that was bundled with the service. (Though 'sample app' is a bit of a stretch, we could really do with a better and simpler sample!)
 
However this now leaves the Java project in a bit of a strange state, it now contains two different build systems and directory structures yet shares one repository and one build. Bugzilla had two different sections for Java and android bugs as well, and I've not yet migrated the android bugs over. Furthermore when using the Android Service you have to reference the Java Library from Maven separately as well which implies a level of separation (Though I would like to see if it's possible to bundle the Java library into the android service at build time to simplify development of applications in the future).
 
Considering all of this, I'd like to split the Android code out of the Java repository and into it's very own one (https://github.com/eclipse/paho.mqtt.android). We'd also split the build into two as well which should be fairly simple. Bugs wouldn't be a problem as they were already segregated in Bugzilla so could be easily migrated into the Android repositories GitHub Issues.
 
Does anybody have any thoughts on this? It shouldn't really effect anyone who consumes the Android service, but will just improve the development of the service itself..
 
Thanks and Kind regards,
 
James Sutton
Software Engineer - IoT Foundation - MQTT Open Source Projects
Technical Trojan - Wimbledon Project
Phone: 01962 815438 | Extension: x372454
E-mail: 
Personal Website: www.jsutton.co.uk
Find me on:      
 IBM

Hursley Park
Hursley, SO212JN
United Kingdom
 
IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev

Back to the top