I am more optimistic then you. here is the idea
https://github.com/barchart/barchart-version-tester/wiki/Maven-OSGI

-------- Original Message --------
Subject: Re: RFP: Version Range Policy
From: David Jencks <david_jen...@yahoo.com>
To: Maven Developers List <dev@maven.apache.org>
Date: Wed 10 Apr 2013 12:44:19 PM CDT
> Can you explain how you think osgi semantic versioning can reasonably be 
> applied to non-osgi-bundles?  It typically takes a project a year or two to 
> figure out what semantic versioning means when converting a project to osgi, 
> I think you would find that trying to apply semantic versioning to non-osgi 
> projects will mean that every update is a major version change.
>
> It would be nice if all projects converted to osgi and used semantic 
> versioning correctly, but I don't think that is going to happen any time soon 
> and I don't think the majority of maven projects will be osgi any time soon.
>
> thanks
> david jencks
> On Apr 10, 2013, at 10:27 AM, Andrei Pozolotin <andrei.pozolo...@gmail.com> 
> wrote:
>
>>    *Maven Developers*
>>
>>    1) This is a formal request to resolve long standing version range
>>    policy problem in maven,
>>    expressed for example in the following ticket:
>>    http://jira.codehaus.org/browse/MNG-3092
>>
>>    THE PROBLEM: LACK OF VERSION RANGE POLICY.
>>
>>    2) I there are no better ideas, I suggest Maven to adopt OSGI
>>    Semantic Version Guidelines.
>>    https://github.com/barchart/barchart-version-tester/wiki/Version-Policy
>>
>>    3) I have working prototype based on maven 3.0.4 with back port of
>>    aether 0.9.0.M2
>>    specifically applied to karaf use case, which could be generalized.
>>    https://github.com/barchart/barchart-maven-karaf-plugin
>>
>>    4) there is an Aries version check plugin, that shows generic java
>>    binary compatibility checks
>>    which should be part of the new maven semantic version contract.
>>    https://github.com/apache/aries/tree/trunk/versioning
>>
>>    Thank you,
>>
>>    Andrei
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Reply via email to