|Re: [paho-dev] Paho repository structure|
Hi,I totally agree with the following structures (I'd just remove the "s"):org.eclipse.paho.mqtt.client.<language>org.eclipse.paho.mqtt.broker.<language>and for the Eurotech contribution, if they agree, I'd use org.eclipse.paho.tooling instead of org.eclipse.paho.esfRegards,Nicolas_______________________________________________I've added a page on the Paho wiki for discussion of the Git repositories that exist, and future requirements.Please feel free to debate here on the mailing list, and over on the wiki itself.In particular:- does it make sense to have MQTT client git repos moved under an org.eclipse.paho.mqtt.clients.<language> structure?- should the Eurotech tooling contribution be under .esf. or should we find a better/more generic name and location - bearing in mind the dependence on the Java client.Thanks.
Andy Piper | Farnborough, Hampshire (UK)
blog: http://andypiper.co.uk | skype: andypiperuk
twitter: @andypiper | images: http://www.flickr.com/photos/andypiper
paho-dev mailing list
Back to the top