Getting back to an old problem. I basically want to add a resolver for RubyGems that does not use all of the fragile workarounds we have in jruby-gradle until now. Basically I want to be able to:
- add a non-maven/ivy repo to
- add some-fu that can translate a group./artifact/version into an appropriate URL for rubygems.
- have it transparent to the user i.e. the script author just want to add something to
Adding something to
repositories, although not trivial is, is easy. It implements ExtensionAware. So no big issue there. The problem comes in the trnalsation from somethign defined ona configuration to actuall requesting it from a repository.
A couple of things I was thinking is:
Component, because that in theory should be queryable via the Artifact Query API. However, how is Gradle even going to be aware o this new
Component. Can a handler be registred for it somewhere.
- Add something that implements
ClientModule. That could be a
DependencyHandler, but I still don’t know if Gradle will recognise this.
Any pointers here will help, even if at this point means hooking up an internal API.