On Aug 10, 2013, at 1106 , Anton Vodonosov avodonosov@yandex.ru wrote:
[…]
What if we then keep contrib/abcl-asdf/maven-embedder.lisp (mostly) unchanged, and just put new code into maven-3.1-embedder.lisp, giving it a separate package.
Then we have
(defmethod abcl-asdf::resolve ((string string)) (if (version> (mvn-version) "3.1") (maven-3.1-embedder:resolve string) (maven-embedder:resolve string))
So, the only thing to factor-out is maven version testing.
Unfortunately, I think that the abstraction is not solely contained in ABCL-ASDF:RESOLVE, but also ABCL-ASDF:RESOLVE-DEPENDENCIES. RESOLVE should be sole entry point, but there are a number of ways I wish to call it (with #: separated ids, with #\ separated ids, with a variable number of strings) that I never have finished working over.
Since getting to this in the "next few days" has proved to optimistic, I have filed a [ticket][328] so people can find the patch as well if they absolute need it in the meantime.
[#328]: http://lisp.not.org/trac/armedbear/ticket/328
-- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."