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 Maven, because they use
code in AbstractWagon (which is hidden by Maven via provider-api).
The options then are
- to push these implementation changes into a new module (thinning
the API down do just the interfaces) that is not filtered by Maven
- require a new version of Maven that updates the wagon api and/or
filters only the interfaces from classloading
What about maintaing binary compatibility? You've made changes as
opposed to pure additions?
Given that the first is a bit of an obtuse separation for this
purpose, and that the current providers have been stable for a year
and a half - I'm opting for the second one.
Any other thoughts on this?
- Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
We all have problems. How we deal with them is a measure of our worth.
-- Unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
