Issue 205 ; updating copyright year in license header to 2011

updating maven plugin and maven report plugin versions

Issue 185 ; applying patch issue185fix.patch

Issue 180 ; rolling back r1008 to r1006

Issue 185 ; applying patch from atdixon with minor changes, list of activities is cleared after activities are processed

Issue 37 ; refactoring package edu.umd.cs.piccolo to org.piccolo2d in core

Issue 172 ; increasing test coverage, javadoc improvements, checkstyle fixes

Fixing Issue 172

Making PNode.print() throw PrinterException rather than swallowing it. ...

This is until we remove printing support from PNode as per Issue 102.

Making checkstyle allow missing javadocs on getters. Leaving it up to the developer to decide if a javadoc is nessary.

Adding Deep Copy Test to PNode.clone()

Removing dead class since all methods that invoked it were deprecated and so have been deleted.

Removing unnecessary local variables from validateFullBounds.

Removing Deprecated code

Deleting PUtilTest since it no longer had any tests

Changing constants to final as per Issue #135

Issue 166 ; improved javadoc comments for moveToFront and related. Fixes issue 166.

Reverting r923 since it was a breaking change. It will need to be redone in 2.0. Seems that some apps were making use of this behaviour.

Applied formatting changes. Eclipse, I love you but...

Fixing error with rounding error bug when calculating inverseTransform repeatedly during globalToLocal. ...

Fixes Issue 159

updating copyright years to include 2010

Fixing Issue #155 by removing check for "isEmpty" on passed bounds to add. ...

This makes add(PBounds) fall in line with the add(x, y) method.

adding @since 1.3 tags in core where clirr report identified new items

adding additional constructor PInterpolatingActivity(long duration)

cleaning up checkstyle warnings introduced by latest refactorings.

Fixing new PMD warnings.

increasing test coverage

As per Issue # 27, I'm making the repainting of the canvas lazier. ...

During an animation it'll record what bounds have actually been dirty, then rather than repainting the entire scene, it'll only paint the region that's been dirtied.

making PCamera internally consistent with regards to layer references, best we can do without making related methods final

adding license headers for core unit tests