Skip to content
This repository has been archived by the owner. It is now read-only.
(Archive, not actively maintained) Run existing Bukkit plugins on Sponge natively
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
ap Update license header date Mar 5, 2016
etc
gradle Update Gradle to 2.11, gitpatcher to 0.8 Feb 14, 2016
lib
patches More fixes Jan 30, 2016
src Mostly updated for SpongeAPI 4.0 Mar 13, 2016
.gitattributes
.gitignore Add patching for Bukkit Jan 31, 2015
.gitmodules Update Gradle to 2.4 and replace SpongeAPI submodule with snapshot de… May 5, 2015
.travis.yml
CONTRIBUTING.md
LICENSE Update license header date Mar 5, 2016
README.md
build.gradle
bukkit.gradle Update SnakeYAML Sep 14, 2015
gradlew
gradlew.bat
settings.gradle Cleanup annotation processor, add brand-new event verifier annotation… Aug 17, 2015

README.md

Pore travis badge

2016/04/19: Pore is officially discontinued. Read more here.


Pore is a plugin for the up-and-coming SpongeAPI built to provide compatibility for Bukkit plugins on the platform. Please note that this project is still under heavy development and is not yet considered functional. Currently, no Bukkit plugins are verified to be supported.

Running Pore on Your Sponge Server

If you like living on the bleeding edge and want to give Pore a try:

  1. Back up your existing system.
  2. Install Sponge, detailed instructions can be found here .
  3. Copy the Pore Snapshot into your server's mods directory.
  4. Make a bukkit-plugins directory in your server's base directory.
  5. Copy any of the plugins you want to try into the bukkit-plugins directory.

When you spin up your server look for messages like:

   [STDERR/sponge]: [name.richardson.james.bukkit.utilities.plugin.AbstractPlugin:onEnable:118]: org.apache.commons.lang3.NotImplementedException: TODO

These aren't an indication that a feature is broken, but that a feature needed for the plugin you're loading hasn't been implemented yet.

Compilation

Gradle is used to handle dependencies.

  • Clone the repo: git clone https://github.com/LapisBlue/Pore.git
  • Navigate to the new directory: cd Pore
  • Compile the project using the Gradle wrapper: ./gradlew (gradlew on Windows)

Running

You can run and debug Pore directly in your IDE if you setup your workspace like described in the following steps:

  1. Setup the Pore project as described in Plugin Debugging and Hotswapping (SpongeDocs)
  2. Create a new run configuration with the same settings as described in the link above, but add this as a program argument: --tweakClass blue.lapis.pore.tweaker.RemapTweaker
  3. Run the server as usual. Pore should load and you should be able to debug in your IDE.

Configuring the annotation processor

Pore uses an annotation processor for event registration. It will be run by the Gradle wrapper by default and IDEA when the project is first built, but if you wish to make changes to event registration, the IDE must be configured to run it on project rebuild. If you don't know what event registration means, skip this step.

For IntelliJ IDEA:

  1. Open File->Settings->Build, Execution, and Deployment->Compiler->Annotation Processors.
  2. Click the Add (plus) button and name the new profile Pore AP.
  3. Click the Pore module under the Default profile and click the Move to button to move it to the Pore AP profile.
  4. In the Processor FQ Name pane, click the Add button and enter the following: blue.lapis.pore.event.EventProcessor
  5. Click Apply. The processor will be run when the project is rebuilt (Build->Rebuild Project).

Questions?

Have an issue or a question about Pore? No problem! Feel free to ask in #lapis on EsperNet.

Licensing

Pore's source code is made available under the MIT license. You may do as you wish with the source within its bounds.

.patch files for Bukkit are made available under the GPLv3.

Pore's distribution is made available under the GPLv3.

You can’t perform that action at this time.