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
I thought he said it was AbstractWagon that had changed, which may
provide protected methods, etc. that aren't in the interfaces...
At any rate, I think I agree with Benjamin, that we should try to
limit (or reduce) the number of AbstractThing super-classes that are
forced into the system b
If we are filtering the interface from classloading...and the interface
has changed, how does that enable the wagons to work with old Mavens?
Are you saying that the changes are backwards compatible already?
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Wednesday,
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
