Just adding a packageinfo (or package-info.java) would help and would not cost
anything. For the Consumer/Provider types ... well, I do not see an easy
solution but would be curious to hear your experiences when you try Andrei
Pozolotin andrei.pozolo...@gmail.com's application at
On 31/07/13 19:11, Raymond Auge wrote:
Also, I would imagine for the initial behavior to only be build warnings
that a developer may be breaking provider/consumer backward
compatibility. I want to grow our team's awareness around the idea of
semantic versionning... not make them want to
On Wed, Jul 31, 2013 at 1:15 PM, Ferry Huberts maili...@hupie.com wrote:
For (semantic) versioning in OSGi the bundle version actually is
meaningless. It's a marketing number, so 6.2.0 in your case.
Only package versions have meaning.
Of course you can always version everything the same,
Hello Ferry,
On 31 Jul 2013, at 19:15 , Ferry Huberts maili...@hupie.com wrote:
For (semantic) versioning in OSGi the bundle version actually is
meaningless. It's a marketing number, so 6.2.0 in your case.
Only package versions have meaning.
We've had this discussion in person before, but
On 31/07/13 20:05, Marcel Offermans wrote:
Hello Ferry,
On 31 Jul 2013, at 19:15 , Ferry Huberts maili...@hupie.com
mailto:maili...@hupie.com wrote:
For (semantic) versioning in OSGi the bundle version actually is
meaningless. It's a marketing number, so 6.2.0 in your case.
Only
Thanks all,
I guess what I was really after was a tool which would actually create all
the packageinfo files for me so I wouldn't have to add them to the hundreds
and hundreds of unversioned packages.
I can script it.
On Wed, Jul 31, 2013 at 2:56 PM, Ferry Huberts maili...@hupie.com wrote:
