CGlib must be in the compile scope, otherwise it's not included.

In addition, updated the README with information about Maven.

ProtocolLib/dependency-reduced-pom.xml

@@ -10,7 +10,7 @@
   <groupId>com.comphenix.protocol</groupId>
   <artifactId>ProtocolLib</artifactId>
   <name>ProtocolLib</name>
-  <version>1.3.1</version>
+  <version>1.3.2</version>
   <description>Provides read/write access to the Minecraft protocol.</description>
   <url>http://dev.bukkit.org/server-mods/protocollib/</url>
   <developers>
@@ -138,7 +138,7 @@
       <groupId>org.bukkit</groupId>
       <artifactId>craftbukkit</artifactId>
       <version>1.3.2-R1.0</version>
-      <scope>compile</scope>
+      <scope>provided</scope>
     </dependency>
     <dependency>
       <groupId>junit</groupId>

ProtocolLib/pom.xml

@@ -165,7 +165,6 @@
   		<groupId>cglib</groupId>
   		<artifactId>cglib-nodep</artifactId>
   		<version>2.2.2</version>
-  		<scope>provided</scope>
   	</dependency>
   	<dependency>
   		<groupId>org.bukkit</groupId>

Readme.md

@@ -17,6 +17,11 @@ lead to more subtle bugs.
 * [JavaDoc](http://aadnk.github.com/ProtocolLib/Javadoc/) 
 
 
+Building
+--------
+You can compile this project yourself by using the latest version of Maven. 
+
+
 A new API
 ---------
 
@@ -33,6 +38,9 @@ as a dependency (or soft-dependency, if you can live without it) to your plugin.
 
     depends: [ProtocolLib]
 
+Future versions will be available in a public Maven repository, possibly on Maven central. But it
+will always be possible to reference ProtocolLib manually.
+
 Then get a reference to ProtocolManager in onLoad() and you're good to go.
 
     private ProtocolManager protocolManager;
@@ -116,7 +124,7 @@ you don't have to create an ArrayList this version:
 Compatiblity
 ------------
 
-One of the main goals of this project was to achive maximum compatibility with craftBukkit. And the end
+One of the main goals of this project was to achieve maximum compatibility with CraftBukkit. And the end
 result is quite flexible - in tests I successfully ran an unmodified ProtocolLib on CraftBukkit 1.8.0, and
 it should be resiliant against future changes. It's likely that I won't have to update ProtocolLib for
 anything but bug and performance fixes.