Skip to main content

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

I am no expert on bundle naming but it might get confusing if you include a version # in the bundle name and actually have a version for number for the number.  For example you could have a situation of  org.eclipse.paho.mqtt.client.v3   


On 6/12/2012 9:44 AM, Nicolas DEVERGE wrote:
And do we need to show the the version of the spec ? ie org.eclipse.paho.mqtt.client.v3.

On Tue, Jun 12, 2012 at 3:33 PM, Nicolas DEVERGE <ndeverge@xxxxxxxx> wrote:

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

Ian Skerrett
VP of Marketing and Ecosystem
Eclipse Foundation
Tel: 613-224-9461 ext 227
Twitter: IanSkerrett

Back to the top