A new CraftBukkit Beta Build (1.5.1-R0.1) that provides Minecraft 1.5.1 compatibility is now available.
Will plugins break with this build?
Provided the developers of the plugins you are using are keeping up with the development of Bukkit, all your plugins should work fine, with the exception of plugins that use Minecraft or CraftBukkit code.
What is a Beta build?
A Beta Build is in between a developer build and a Recommended Build. These builds simply work and are promoted much more frequently than a Recommended Build. While we will do some testing before promoting a beta build, we will not be running it through our extensive test process. As such, there are no guarantees that they will not contain minor bugs. If we do find out they are broken, we will mark it as such on DLB and promote a new one. A beta build may contain incomplete API and new features but they should not interfere with running the build in any way.
A little over a week ago we announced some of the improvements across the Bukkit project on which we have been working. One of the issues we touched upon was the unacceptable delay the community has been experiencing when it came to getting their pull requests into the project - or, in some cases, even getting a response. Unfortunately, we reached a point where we were not equipped to handle the bulk of the pull requests we were receiving and the entire queue stalled as a result. The Bukkit project is no stranger to community contributions and the clear benefits of fully utilising them: many of the features Bukkit has to offer are thanks to contributions from the community, so addressing this bottleneck is extremely important for us.
The Pull Request Handling Improvements Initiative
The Pull Request Handling Improvements initiative consists of several big and important changes to the way we handle code contributions from the community. One key aspect of this initiative is...
A CraftBukkit development build with Minecraft 1.5 compatibility is now available!
This build is COMPLETELY UNSUPPORTED so if you're not ready to deal with any bugs or issues that might crop up from running a development build, you should not be running it. We will be deleting any questions asking how to get this usable. If you have to ask where or how to get the development build, you should NOT be running it and posts of that nature will be deleted.
If you're okay with running, are able to run a development build and want to help us get to a beta and RB sooner, please run this build and report any bugs you find on our issue tracker, Leaky. Please remember, the quality of this build is simply "it compiles!".
Known Issues:
Falling blocks spawn (or appear to spawn) one block higher than they should. This is a vanilla bug and needs to be fixed by Mojang.
When observing a player riding a vehicle or pig, they appear to teleport around the area of the vehicle...
The Bukkit project prides itself on being community built and driven. Unfortunately we were simply overwhelmed by the insatiable desire of our community to get involved with, and give back to, the Bukkit project. Moving forward, to address this concern, we have a few proposed changes which we hope will instill a renewed sense of community and getting involved.
Increased focus on JavaDocs and project documentation:
An API is only as useful and powerful as the documentation supporting it. Documentation is the foundation which developers depend on for correct and appropriate usage of an API. It is an aspect of the project which should have been given more attention from the beginning. Unfortunately, as is the case with most open source projects, we made the mistake of putting the importance of well documented code on the sidelines and, as a result, the usability of our API suffered. The JavaDoc Proposal Initiative is part of our effort to improve and complete our API’s...
