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
I would deal with this same way osgi does: guidelines, annotations, tools.
example:
* be clear if your jar is API artifact vs API consumer artifact vs API
provider artifact.
* @ConsumerType and @ProviderType will tell people what to expect.
* enforcement plugins will quickly educate about the dist
so you are basically saying all packages are exported. I think you will find
that few meaningful code changes will result in a non-major-version change
whether or not the intended api changes. Have you tried this out with some
real non-osgi projects to see what versions you'd come up with and
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 how y
Hi,
The vote has passed with the following result :
+1 (binding): Olivier, Hervé, Kristian
+1 (non binding): Andreas
I will promote the artifacts to the central repo.
Kristian
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apa
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
Ok, trying a different browser (Safari) solved this. Not sure what firefox
is sending to trigger a json answer.
/Anders
On Wed, Apr 10, 2013 at 9:26 AM, Anders Hammar wrote:
> I get a json answer. Not the UI I was expecting...:-)
>
> /Anders
>
>
> On Wed, Apr 10, 2013 at 9:16 AM, Olivier Lamy
I get a json answer. Not the UI I was expecting...:-)
/Anders
On Wed, Apr 10, 2013 at 9:16 AM, Olivier Lamy wrote:
> try https://cms.apache.org/maven/
>
> I have just fixed that in the documentation.
>
> 2013/4/10 Anders Hammar :
> > The instructions says navigate to https://cms.apache.org/mav
try https://cms.apache.org/maven/
I have just fixed that in the documentation.
2013/4/10 Anders Hammar :
> The instructions says navigate to https://cms.apache.org/maven to edit the
> web site. But I get a 404 for the URL. Should it work or is it the wrong
> URL?
>
> /Anders
--
Olivier Lamy
E
The instructions says navigate to https://cms.apache.org/maven to edit the
web site. But I get a 404 for the URL. Should it work or is it the wrong
URL?
/Anders
11 matches
Mail list logo
