anchor.diff:  }
   
   dependencies {
  -    gems group: 'com.lookout', name: 'custom-gem', version: '1.0.+'
  +    gems 'rubygems:my-custom-gem:1.0.1'
   }
   ----
   
  
positive.code: [source,gradle]
  ----
  jruby {
      defaultRepositories = false
  }
  
  repositories {
  
negative.code: 
  == Advanced Usage
  
  === Using the built-in Gem proxy
  
  As of version 1.1.0, the JRuby/Gradle base plugin supports embedding a
  link:https://github.com/torquebox/rubygems-servlets[rubygems-servlets] process
  *inside* the Gradle process itself. This obviates the need for a third-party
  proxy to present the Maven-compatible dependency information that JRuby/Gradle
  relies on.
  
  .build.gradle
  [source,gradle]
  ----
  apply plugin: 'com.github.jruby-gradle.base'
  
  /* Disable our default repositories */
  jruby.defaultRepositories false
  
  repositories {
      rubygems('https://rubygems.org')
  }
  
  dependencies {
      gems 'rubygems:sinatra:1.4.5'
  }
  ----
  
  === Using a custom Gem repository
  
  By default the jruby plugin will use
  link:http://rubygems.lasanga.io[rubygems.lasanga.io] as its source of Ruby
  gems. This is a server operated by link:https://github.com/rtyler[R. Tyler
  Croy] and it presents a Maven repository of the data from
  link:https://rubygems.org[rubygems.org].
  
  If you **do not** wish to use this repository, you can run your own Maven proxy
  repository for either rubygems.org or your own gem repository by running the
  link:https://github.com/torquebox/rubygems-servlets[rubygems-servlets] server.
  
  You can then use that custom Gem repository with:
  
  