NPanday - Visual Studio Integration for Maven

2008-12-03 Thread Brett Porter
Hi, For those not on nmaven-dev that might be interested... After the termination of the NMaven podling in the incubator, a continuation of the 0.14 branch has been started at Codeplex called NPanday: http://www.codeplex.com/npanday The project is composed of Visual Studio integration for

Proposed change to handling of dependency version ranges

2008-12-03 Thread Ian Robertson
I would like to propose a change to how maven handles version ranges such as [1.0,), as described in

What will replace the @aggregator MOJO configuration?

2008-12-03 Thread Nick Pellow
Hi, I noticed that the 'aggregator' parameter for a MOJO is slated for deprecation in a future release of Maven. http://books.sonatype.com/maven-book/reference/writing-plugins.html#d0e22494 What should be used instead, to fulfill the following use-case: - a multi-module project, which would

Re: Proposed change to handling of dependency version ranges

2008-12-03 Thread Christian Schulte
Ian Robertson schrieb: I would propose that the semantics change to Of the overlapping ranges, the *lowest* soft requirement is the version to be used. Consequently, new releases of a project would not change builds of other projects depending on it (assuming that version numbers

Re: Proposed change to handling of dependency version ranges

2008-12-03 Thread Jason van Zyl
We cannot change the behavior, or really even attempt to fiddle with the code in 2.0.x. We are also planning on entirely replacing this code with Mercury in the 3.x line. Apache SVN is down so I'll point you to Mercury when it comes back. Oleg is the one who has implemented Mercury so he

Re: Proposed change to handling of dependency version ranges

2008-12-03 Thread Oleg Gusakov
Dear All, Jason van Zyl wrote: We cannot change the behavior, or really even attempt to fiddle with the code in 2.0.x. We are also planning on entirely replacing this code with Mercury in the 3.x line. Apache SVN is down so I'll point you to Mercury when it comes back. Oleg is the one who has

Re: Proposed change to handling of dependency version ranges

2008-12-03 Thread Barrie Treloar
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 releases of a project would not change builds of other projects depending

Re: Proposed change to handling of dependency version ranges

2008-12-03 Thread Stephen Connolly
2008/12/4 Barrie Treloar [EMAIL PROTECTED] There is talk about a plugin (can't recall which) that can lock down the version of plugins and also tell you if newer versions are available, so you can selectively decide to upgrade. But I am not sure if such a plugin exists yet. That would be