no time to work on it for the moment: my list is already full for at least a
week or 2 to be able to release Maven 3.1-alpha-1 and everything necessary
but I probably will work with you on this topic after that: I don't know if I
will agree with everything, but having some new ideas and proof of
distinctions.
since maven is "convention over configuration", this should work.
"Have you tried " - not yet, about to start :-). please share your
experience.
Original Message --------
Subject: Re: RFP: Version Range Policy
From: David Jencks
To: Maven Developers Li
/Maven-OSGI
>
> Original Message ----
> Subject: Re: RFP: Version Range Policy
> From: David Jencks
> To: Maven Developers List
> Date: Wed 10 Apr 2013 12:44:19 PM CDT
>> Can you explain how you think osgi semantic versioning can reasonably be
>> applied t
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
To: Maven Developers List
Date: Wed 10 Apr 2013 12:44:19 PM CDT
> Can you explain
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
*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 i
