|Re: [paho-dev] plan for java client?|
On 5/2/2014 4:03 PM, Ian Craggs wrote:
That looks great to me.
You are moving the version from 0.4.1 to 0.9.0? I have no objections if that numbering fits the needs of project...I just wanted to make sure it was intentional. You generally *don't* want to have the bundle level versioning track the feature-or-release-level versioning (if you do, it can/will become a maintenance burden in my experience...plus you want to have the bundle-level versioning be based as much as possible on OSGi semantic versioning ...for each of your bundle APIs separately. But you are obviously all pre-version-1.0.0 right now anyway...so it's not really that big a deal...until you reach 1.0.0.
BTW...one thing...as for the version attributes associated with the Export-Package...I would recommend *not* including the qualifier in those attributes, but rather just the major.minor.micro...e.g:
Well, one reason it would have to be singleton is if you had a plugin.xml in there...it was an eclipse plugin...and were using the extension registry (in Eclipse). But I don't see any plugin.xml in your bundle...there's no bundle activator...and I don't obviously see any other code that requires it to be a singleton...so you might be able to remove the singleton attribute.
Well, there are plenty of Maven/Tycho gurus around EF projects, but I'm not one of them ;-). I would personally be inclined to ask for assistance on cross-projects mailing list...and/or David Williams directly (don't tell him I said that).
That's great...thanks much.
and Swing sample GUI application (which may not be as it is meant to be run standalone).
Sounds great! If I can help further, please let me know.
Back to the top