Skip to content

Latest commit

 

History

History
69 lines (49 loc) · 1.93 KB

implementation.rst

File metadata and controls

69 lines (49 loc) · 1.93 KB

Internal Sponge Classes

You can add SpongeCommon, SpongeVanilla or SpongeForge as a dependency to your plugin project if you need to access internal Sponge classes.

Warning

You should only add a specific implementation dependency when really necessary. If possible, use SpongeAPI or request feature additions on the SpongeAPI issue tracker.

In addition to the normal artifacts, the implementation modules provide a dev artifact which can be easily used in the IDE, since it is not re-obfuscated. All implementation modules have the API module already included, so you do not need an extra dependency on SpongeAPI.

SpongeCommon

  • Group ID: org.spongepowered
  • Artifact ID: spongecommon
  • Version: Same as SpongeAPI
  • Classifier: dev

Example Using Gradle

dependencies {
    compile 'org.spongepowered:spongecommon:5.0.0-SNAPSHOT:dev'
}

SpongeVanilla

Choose a build from the downloads page and copy the full version string to your dependency definition.

  • Group ID: org.spongepowered
  • Artifact ID: spongevanilla
  • Version: Use a build version from the downloads page
  • Classifier: dev

Example Using Gradle

dependencies {
    compile 'org.spongepowered:spongevanilla:1.8.9-4.2.0-BETA-348:dev'
}

SpongeForge

Choose a build from the downloads page and copy the full version string to your dependency definition.

  • Group ID: org.spongepowered
  • Artifact ID: spongeforge
  • Version: Use a build version from the downloads page
  • Classifier: dev

Example Using Gradle

dependencies {
    compile 'org.spongepowered:spongeforge:1.8.9-1890-4.2.0-BETA-1625:dev'
}