Subject: [Armedbear-devel] abcl-asdf: merged changes from Cyrus
From: Mark Evenson <[email-masked]>
To: [email-masked]
Date: Mon, 5 Jan 2015 18:46:20 +0100
List-Id: <armedbear-devel.common-lisp.net>

[Cyrus’s recent patches for ABCL-ASDF to use alternate Maven repositories and other fixes][1] have been merged [into the ABCL trunk][2,3,4,5].

[I made the following deviation from the patches][6]:
The codes seems to intend to record, buts fails to actually set, the repository an artifact is download from as part of the path.  I changed the ineffective code as a comment, mainly as the MVN path is intended to follow the [MVN URI scheme][7] for which the repository definitely doesn’t belong at the end but rather at the beginning. 

Instead of 

   group-id/artifact-id/version/repository-url

it would be
   
   repository-url!group-id/artifact-id/version

But I don’t have enough of the details in my head to know if we really need to record the repository-url in the path.  I suspect that including the repository URL might be necessary for subsequent invocations to check the freshness, but the current code seems to work.  More investigation should be necessary.

[1]: https://github.com/slyrus/abcl/commits/abcl-asdf-maven-enhancements-cleanup
[2]: http://abcl.org/trac/changeset/14742
[3]: http://abcl.org/trac/changeset/14743
[4]: http://abcl.org/trac/changeset/14744
[5]: http://abcl.org/trac/changeset/14745
[6]: http://abcl.org/trac/changeset/14742/trunk/abcl/contrib/abcl-asdf/abcl-asdf.lisp
[7]: https://ops4j1.jira.com/wiki/display/paxurl/Mvn+Protocol

-- 
"A screaming comes across the sky.  It has happened before but there is nothing 
to compare to it now."

_______________________________________________
Armedbear-devel mailing list
[email-masked]
http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel