On 15/05/2008, at 12:22 AM, Benjamin Bentmann wrote:
If I don't misunderstand things, the same problems could arise some
day for
the AbstractMojo from the maven-plugin-api.
Yeah, though in that case there's a more direct tie between the
version of Maven and the plugin API than in this c
On 14-May-08, at 5:29 AM, Brett Porter wrote:
Hi,
I'm running through the issues in Wagon to get towards another
release. On trunk there are already a couple of changes to the
AbstractWagon. In doxia-like fashion, this prevents being able to
use a new wagon with existing versions of Mave
Developers List
Subject: wagon API upgrades
Hi,
I'm running through the issues in Wagon to get towards another
release. On trunk there are already a couple of changes to the
AbstractWagon. In doxia-like fashion, this prevents being able to use
a new wagon with existing versions of Maven, b
, May 14, 2008 8:29 AM
To: Maven Developers List
Subject: wagon API upgrades
Hi,
I'm running through the issues in Wagon to get towards another
release. On trunk there are already a couple of changes to the
AbstractWagon. In doxia-like fashion, this prevents being able to use
a new wagon
Brett Porter wrote:
In doxia-like fashion, this prevents being able to use a new wagon with
existing versions of Maven, because they use code in AbstractWagon (which
is hidden by Maven via provider-api).
If I don't misunderstand things, the same problems could arise some day for
the Abstract
Hi,
I'm running through the issues in Wagon to get towards another
release. On trunk there are already a couple of changes to the
AbstractWagon. In doxia-like fashion, this prevents being able to use
a new wagon with existing versions of Maven, because they use code in
AbstractWagon (whic