Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support artifact resolvers to load libraries not published to maven central #80

benhutchison opened this issue May 8, 2015 · 3 comments


Copy link

@benhutchison benhutchison commented May 8, 2015

Support artifact resolvers to load libraries that are not published to maven central.

There is one existing attempt to do so, by @alexarchambault #66 However, Li Haoyi wasn't willing to accept with alot of unfocused/poorly understood code lifted out of SBT.

Copy link

@lihaoyi lihaoyi commented May 14, 2015

Possible solution that doesn't involve taking on gobs of magic code: send a PR to
hard code the handful you care about and be done with it ^_^

Copy link

@hohonuuli hohonuuli commented Aug 12, 2015

Just a note that hard-coding support for the local maven repo at "~/.m2/repository" as a default resolver would be extremely useful.

@lihaoyi lihaoyi added the help wanted label Aug 16, 2015
Copy link

@lihaoyi lihaoyi commented Aug 16, 2015

This should be a pretty trivial change if anyone wants to hardcode anything; we could also lift IvyThing from a top-level-object into a class, have an instance belonging to each Interpreter, and have it expose a Ref through ReplAPI so people can modify it in the REPL

etorreborre added a commit to etorreborre/Ammonite that referenced this issue Dec 10, 2015
@lihaoyi lihaoyi closed this in 0d319f5 Dec 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.