Skip to content

Plugin Rename Rules

Jump to bottom
Jon Schneider edited this page May 11, 2016 · 1 revision

The Nebula suite of Gradle plugins preceded the introduction of the Gradle plugin portal, and so preceded the naming standard that came along with the plugin portal. Unfortunately, these plugins must support both their legacy name and fully qualified name. This set of rules helps to migrate builds to the new names.

To apply all current (and future) renames that we pack with lint, add the all-renames rule:

gradleLint.rules += 'all-nebula-renames'

Plugin renaming is also one of the simplest possible rules to implement, which is why they were one of the first rules we implemented!

The set of renames currently included is:

  • nebula.clojure
  • nebula.deb
  • nebula.dependency-lock
  • nebula.facet
  • nebula.gradle-git-scm
  • nebula.info-ci
  • nebula.info
  • nebula.integtest
  • nebula.ospackage-application-daemon
  • nebula.ospackage-application
  • nebula.ospackage-daemon
  • nebula.ospackage
  • nebula.override
  • nebula.gradle-stash
Clone this wiki locally