Re: Proposed change to handling of dependency version ranges

2008-12-08 Thread Jörg Schaible
Hi Ian, Ian Robertson wrote at Montag, 8. Dezember 2008 20:35: > On Wed, 2008-12-03 at 23:38 -0700, Barrie Treloar wrote: [snip] >> I think the short answer is, if you want repeatable builds then don't >> use range syntax. >> By defining a range you are saying that everything that fits in this

Re: how to define mirror configurations in top level pom

2008-12-08 Thread Brett Porter
I think this question is more relevant for [EMAIL PROTECTED] To answer briefly, it's not possible. You can declare repositories in the parent POM, however mirrors/repository managers are an environment setting specific to the user and used regardless of the project, so it goes in the user's

how to define mirror configurations in top level pom

2008-12-08 Thread Harsha Godugu
Can anybody tell me how one can define maven mirrorOf settings in top level pom directly. (I am aware of how to do that using settings.xml) Is this possible with latest maven (2.0.9)? The idea is, every project will have certain predefined settings that are constant to that project itself and

Mercury ant wrapper

2008-12-08 Thread Oleg Gusakov
Whoever might be interested, and especially Herve: I am putting together a simplified ant wrapper for Mercury. Can you please critique http://jira.codehaus.org/browse/MERCURY-48 ? Main idea - create a simple to use syntax, yet being able to extend it to full power of Mercury. The game plan is

Re: Proposed change to handling of dependency version ranges

2008-12-08 Thread Ian Robertson
On Wed, 2008-12-03 at 23:38 -0700, Barrie Treloar wrote: > On Thu, Dec 4, 2008 at 11:06 AM, Ian Robertson <[EMAIL PROTECTED]> wrote: > > I would propose that the semantics change to "Of the overlapping ranges, > > the *lowest* soft requirement is the version to be used." Consequently, > > new re

Re: Proposed change to handling of dependency version ranges

2008-12-08 Thread Ian Robertson
If I understand the web page correctly, if Mercury sees a dependency of 1.23, it will interpret that to mean "any version 1.23 or or greater". What I'm unable to discern from the links below is which version will actually be chosen when the versions available are, say, 1.23 and 1.24. Is there

Re: Preparation of Doxia 1.0-beta-1 release

2008-12-08 Thread Benjamin Bentmann
Vincent Siveton wrote: The tests are to perform XSD validations under our current documentation. Since we add new XSD files in this release, I think these tests are useful. No doubt, tests are useful but I feel we mix two different test targets here: a) correctness of the XSDs b) correctnes

Re: Reports are down

2008-12-08 Thread Arnaud HERITIER
Hi David, Ok, I'll try to see what they changed in their remote API to propose to you a patch. cheers. Arnaud On Mon, Dec 8, 2008 at 12:09 AM, David Blevins <[EMAIL PROTECTED]>wrote: > A patch would be great! > > Sent from my iPhone > > > On Dec 7, 2008, at 1:36 AM, "Arnaud HERITIER" <[EMA

Re: {VOTE] Release Mercury 1.0.0-alpha-2

2008-12-08 Thread Jason Dillon
+1 --jason On Dec 8, 2008, at 2:18 PM, Oleg Gusakov <[EMAIL PROTECTED]> wrote: Dear All, This is the first release of Mercury with all major [mercury] functionality enabled: repository access + dependency resolution. You can try using it for resolving artifacts and then writing them