Re: Maven and ABCL
Mark Evenson <[email protected]>
| Newsgroups | gmane.editors.j.devel |
|---|---|
| Message-ID | <[email protected]> |
On 4/7/17 17:50, Alan Ruttenberg wrote: > I'm using :mvn ASDF components and ran into a problem with having multiple > versions of the same library. The issue boils down to the fact that ABCL > currently processes dependencies for :mvn components one at a time, which > doesn't take into account mutual dependencies. Attached is a > function resolve-multiple-maven-dependencies, which takes a set of maven > components and computes the dependencies. […] > The attached code also has features not yet supported by the :mvn syntax > that are really needed: The ability to override versions of a particular > dependency that a downstream dependency specifies, and the ability to > exclude certain artifacts altogether. > > Mark has suggested that the maven resolution could be moved to the ASDF > planning stage, which sounds like a good idea. […] I have [updated abcl-1.5.0 to][maven-3.2.1] which should serve as a good basis for work on pushing the resolution into the ASDF planning layer. In addition, [t/maven][] contains Alan's test code to follow along at home. [asdf-3.2.1]: https://gitlab.common-lisp.net/abcl/abcl/commit/a479be0771b037b091bfc75e163000fcb28f3a89 [t/maven]: https://gitlab.common-lisp.net/abcl/abcl/commit/4247dfe96284fb90faced00da1e30d92bf43e2e6 -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."