-
Notifications
You must be signed in to change notification settings - Fork 382
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
add aliases for standard repositories #6979
Comments
dup of #6954 |
Maybe It fails to load because it's deposited on jcenter and not on maven central? |
Hi Tip: look at https://github.com/jitpack/jitpack.io#publishing-on-jitpack and "Some extras to consider" |
Cool thanks, what about mvn local or jcenter. Are there resolvers for these as well? Like
Especially test changes locally, this would be super useful. |
Found half of the answer myself in a recent comment o #6583. To add the local maven cache, the user needs to configure a resolver with:
Not sure why |
Cool. It's not the default because unfortunately maven doesn't support concurrent access, so if we used the default location then the user could break BeakerX if they were doing development in a terminal or IDE at the same time as running BeakerX. See #6340. I do like your idea for a mvnlocal resolver, will try to get it in the next release: #6986. |
Thanks. Users may want to fetch such dependencies from jcenter. E.g. the above mentioned krangl is hosted there. Is there a dedicated resolver for jcenter as well? |
There isn't, but I don't mind adding a shortcut to jcenter, like gradle has, so you don't have to type or remember the URL. Is there a list of all/most such repositories that we can just pull in? I don't really want to the maintainer and arbiter of such a thing. |
Not sure, but https://docs.gradle.org/current/userguide/repository_types.html#sub:maven_jcenter seems a good reference. |
If there are built-in aliases, maybe also jitpack? |
this makes me think, is it be possible to support `%gradle` and be done
with it?
|
%classpath add mvn de.mpicbg.scicomp:krangl:0.7
The text was updated successfully, but these errors were encountered: