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 AbstractMojo from the maven-plugin-api.
- to push these implementation changes into a new module (thinning the
API down do just the interfaces) that is not filtered by Maven
Such as separation exists already for maven-reporting-api and
maven-reporting-impl so this approach doesn't seem that odd.
Anyway, +1 on decoupling implementation classes from the version of the
Maven core. Keeping interfaces stable is hard enough, doing the same for
utility/convenience classes is not easier and may slow down improvements.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
