SteamWar/Paper
13
0
Fork 0
geforkt von Mirrors/Paper
Code Issues Pull-Requests 1 Aktivität
6492eb9683
Paper/paper-api
Verlauf
Bukkit/Spigot 6492eb9683 [Bleeding] Cleanup of exceptions org.bukkit.plugin.Invalid* 
Removed throwable and message, because the superclass already stores them
Added message of inner exception to the outer exception to make the first line of the stacktrace more verbose

By: Zeerix <zeerix@draig.de>
2012-02-11 02:16:16 +01:00
..
src [Bleeding] Cleanup of exceptions org.bukkit.plugin.Invalid* 2012-02-11 02:16:16 +01:00
.gitignore IntelliJ is awesome. 2011-07-05 00:14:31 -04:00
LICENCE.txt We're GPL. 2011-01-02 10:57:42 +01:00
pom.xml Updated version to 1.1-R4-SNAPSHOT for development towards next release. 2012-01-30 04:00:42 -05:00
README.md Updated README for line-ending demands, also fixed line-endigs. 2011-04-25 13:24:32 +02:00

README.md

Bukkit

A Minecraft Server API.

Website: http://bukkit.org
Bugs/Suggestions: http://leaky.bukkit.org

Compilation

We use maven to handle our dependencies.

  • Install Maven 3
  • Check out this repo and: mvn clean install

Coding and Pull Request Conventions

  • We generally follow the Sun/Oracle coding standards.
  • No tabs; use 4 spaces instead.
  • No trailing whitespaces.
  • No 80 column limit or midstatement newlines.
  • No CRLF lineendigs, LF only, put your gits 'core.autocrlf' on 'true'
  • Proper javadoc for each method added/changed to describe what it does.
  • The number of commits in a pull request should be kept to a minimum (squish them into one most of the time - use common sense!).
  • No merges should be included in pull requests unless the pull request's purpose is a merge.
  • Pull requests should be tested (does it compile? AND does it work?) before submission.

Follow the above conventions if you want your pull requests accepted.