Hi,
Main reason for this release - bug fixes. A lot of testing done on the
repository side, IT coverage on repository components is 60-70 %
We solved 11 issues:
http://jira.codehaus.org/browse/MERCURY/fixforversion/14955
Staging repo:
https://repository.apache.org/content/repositories/maven-s
+1
Brian E. Fox wrote:
It's finally time after 8 Release Candidates:
Issues fixed:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName
=Html&projectId=10500&Create=Create
NOTE: The urls below are using a self-signed certificate.
There is an issue requesting an o
+1
On 9-Feb-09, at 11:32 PM, Brian E. Fox wrote:
It's finally time after 8 Release Candidates:
Issues fixed:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName
=Html&projectId=10500&Create=Create
NOTE: The urls below are using a self-signed certificate.
There is an
I did, and gave up trying to change them.
-Original Message-
From: Jamie Whitehouse [mailto:basil.whiteho...@genesyslab.com]
Sent: Tuesday, February 10, 2009 9:41 AM
To: Maven Developers List
Subject: RE: [vote] release maven 2.0.10
In case you didn't notice, URLs are still wrapped.
On
+1 (non-binding)
The ZIP binary worked fine for my builds.
at work, at home, and the archetype-plugin build.
Thanks,
Raphaël
2009/2/10 Brian E. Fox
> It's finally time after 8 Release Candidates:
>
>
>
> Issues fixed:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleN
Sent from my [rhymes with myPod] ;-)
On 10 Feb 2009, at 19:05, Jason van Zyl wrote:
On 10-Feb-09, at 1:06 PM, Stephen Connolly wrote:
2009/2/10 Jason van Zyl :
On 10-Feb-09, at 11:33 AM, Stephen Connolly wrote:
2009/2/10 Jason van Zyl :
On 10-Feb-09, at 8:37 AM, Stephen Connolly wrot
On 10-Feb-09, at 1:06 PM, Stephen Connolly wrote:
2009/2/10 Jason van Zyl :
On 10-Feb-09, at 11:33 AM, Stephen Connolly wrote:
2009/2/10 Jason van Zyl :
On 10-Feb-09, at 8:37 AM, Stephen Connolly wrote:
Which is why I think that the rules need to be defined at the
repository, and per gro
2009/2/10 Jason van Zyl :
>
> On 10-Feb-09, at 11:33 AM, Stephen Connolly wrote:
>
>> 2009/2/10 Jason van Zyl :
>>>
>>> On 10-Feb-09, at 8:37 AM, Stephen Connolly wrote:
>>>
Which is why I think that the rules need to be defined at the
repository, and per groupId
>>>
>>> That's just
On 10-Feb-09, at 11:33 AM, Stephen Connolly wrote:
2009/2/10 Jason van Zyl :
On 10-Feb-09, at 8:37 AM, Stephen Connolly wrote:
Which is why I think that the rules need to be defined at the
repository, and per groupId
That's just a nightmare. What's wrong with just settling on
something
Brian E. Fox wrote:
Once multiple resolution strategies start appearing, life will be
infinitely more complicated.
yes :( I think Mercury has a pretty decent potential to cover majority
of the reasons to change version comparisons. For example - there is a
notion of version quality and reposit
2009/2/10 Jason van Zyl :
> On 10-Feb-09, at 8:37 AM, Stephen Connolly wrote:
>
>> Which is why I think that the rules need to be defined at the
>> repository, and per groupId
>>
>
> That's just a nightmare. What's wrong with just settling on something that
> works for everyone. I really and truly
Christian Schulte schrieb:
> Stephen Connolly schrieb:
>> What I'm thinking is that if we had some metadata associated with the
>> groupId, it could specify what the version comparison rule is for that
>> groupId (and all it's child groupIds)...
>
> It would be very cool to have some general purpo
Stephen Connolly schrieb:
> What I'm thinking is that if we had some metadata associated with the
> groupId, it could specify what the version comparison rule is for that
> groupId (and all it's child groupIds)...
It would be very cool to have some general purpose grouplevel metadata!
Various thin
Sorry, false alarm. I missed an update when I built that version of
maven locally.
Benjamin Bentmann wrote:
John Casey wrote:
and I have:
[...]
stringParams.1=test
stringParams=2
stringParams.0=test
[...]
Which expresses the bug MNG-4023 is about, i.e. the profile from the
test parent POM
On 10-Feb-09, at 8:37 AM, Stephen Connolly wrote:
Which is why I think that the rules need to be defined at the
repository, and per groupId
That's just a nightmare. What's wrong with just settling on something
that works for everyone. I really and truly can't honestly see how the
OSGi ver
In case you didn't notice, URLs are still wrapped.
On Mon, 2009-02-09 at 23:54 -0500, Brian E. Fox wrote:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName
> =Html&projectId=10500&Create=Create
On 10-Feb-09, at 8:56 AM, Wendy Smoak wrote:
On Tue, Feb 10, 2009 at 6:26 AM, Paul Benedict
wrote:
Will the download page be updated to contain this? 2.1-M1 is
there ...
kind of makes sense to me 3.0 should be there too.
Jason mentioned he doesn't recommend anyone try it just yet, so I
w
Not until we think it's ready for a wider audience. The criterion for
that will be we can't find any projects that won't run on 3.0. The
point at which that happens it will be generally worth people trying
it. Before that I honestly think it's a waste of their time. As the
alphas proceed to
Probably but I'm just leaving all the crap there that the release
produces. I'll figure out why the tool is producing that or what
happened and fix that.
The apache-maven-* bits should be excluded but I'm not sure what made
the empty directories. That why we're going to have a _lot_ of alph
On Tue, Feb 10, 2009 at 6:26 AM, Paul Benedict wrote:
> Will the download page be updated to contain this? 2.1-M1 is there ...
> kind of makes sense to me 3.0 should be there too.
Jason mentioned he doesn't recommend anyone try it just yet, so I
wouldn't put it on the download page which is inten
Which is why I think that the rules need to be defined at the
repository, and per groupId
2009/2/10 Brian E. Fox :
> Once multiple resolution strategies start appearing, life will be
> infinitely more complicated. If you use a different strategy and I
> consume your artifacts, I need to be able to
Once multiple resolution strategies start appearing, life will be
infinitely more complicated. If you use a different strategy and I
consume your artifacts, I need to be able to interpret your strategy and
use it when calculating your part of the tree. (and someone else's etc).
That means the strat
Will the download page be updated to contain this? 2.1-M1 is there ...
kind of makes sense to me 3.0 should be there too.
Paul
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@m
Hi Brett,
I was thinking, to avoid this mistake, we should add ranges to all the
previous ITs and then remove the default constructor. WDYT?
No objections from my side.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@mav
On 10/02/2009, at 5:29 PM, bentm...@apache.org wrote:
Author: bentmann
Date: Tue Feb 10 09:29:15 2009
New Revision: 742910
URL: http://svn.apache.org/viewvc?rev=742910&view=rev
Log:
o Added proper version range to IT
I was thinking, to avoid this mistake, we should add ranges to all the
pr
On 07/02/2009, at 2:43 AM, John Casey wrote:
Can we implement modello's identity/identifier element in maven.mdo
rather than hand-coding the identity methods?
getKey() here is a method, since the identifier is a composite
(groupId + ":" + artifactId). I added a test to make sure the curren
Hi Shane,
Author: sisbell
Date: Mon Feb 9 22:00:52 2009
New Revision: 742760
URL: http://svn.apache.org/viewvc?rev=742760&view=rev
Log:
Fixed path problem on unit test.
Modified:
maven/components/trunk/maven-project/src/test/java/org/apache/maven/project/builder/PomConstructionTest.java
John Casey wrote:
and I have:
[...]
stringParams.1=test
stringParams=2
stringParams.0=test
[...]
Which expresses the bug MNG-4023 is about, i.e. the profile from the
test parent POM was injected two times instead of only once.
I try to catch you in IRC later this day so we can have a close
2009/2/9 Benjamin Bentmann :
> Olivier THIERRY wrote:
>
>> This plugin should create a file referred by "targetFile" property by
>> reading and merging files referred by "sourceFiles" property. Source
>> files are in Maven project dependencies.
>> So I need to get an input stream on these source fi
Jason van Zyl wrote:
http://www.apache.org/dist/maven/binaries/
There are some files that could probably be deleted. E.g. an empty
3.0-alpha-2 directory, apache-maven-3.0-alpha-2.pom* and
apache-maven-3.0-alpha-2.jar*.
Benjamin
OK, here's a hairy old chestnut...
Maven has a set of version comparison rules... they don't work for
everyone... well life sucks
Mercury has a new set of version comparison rules... they're a lot
better, but probably don't work for everyone... life still sucks...
I've been thinking, the reality
31 matches
Mail list logo
