Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] Paho repository structure

The ESF and Apps repositories were the initial take and do not seem to fit anymore.

"tooling" is good but Chad should weigh in on that too.

Also, we should see what Arlen thinks as he is planning what I would call an application framework that spans the client and the server, so we should be sure the new repository naming fits with that.


From:        Nicolas DEVERGE <ndeverge@xxxxxxxx>
To:        General development discussions for paho project <paho-dev@xxxxxxxxxxx>
Date:        06/12/2012 09:39 AM
Subject:        Re: [paho-dev] Paho repository structure
Sent by:        paho-dev-bounces@xxxxxxxxxxx


I totally agree with the following structures (I'd just remove the "s"):

and for the Eurotech contribution, if they agree, I'd use org.eclipse.paho.tooling instead of org.eclipse.paho.esf


On Tue, Jun 12, 2012 at 3:13 PM, andypiperuk@xxxxxxxxx <andypiperuk@xxxxxxxxx> wrote:
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.


Andy Piper | Farnborough, Hampshire (UK)
blog:   |   skype: andypiperuk
twitter: @andypiper  |  images:

paho-dev mailing list


paho-dev mailing list

Back to the top