adding verified issue 155 to ReleaseNotes.txt

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.

updating version to 1.3-beta

Issue 146 ; additional maven plugin configuration

Unnecessary import.

Modifying SwingLayoutNode so that it accepts a Container during construction. Otherwise, creating a node that uses BoxLayout is impossible without making the node's layout mutable.

Removing setLayout method. Effectively making the layout final.

Stab 2, easy redundant public modifiers.

First attack on checkstyle.

Initial import of code for Issue #150.

Issue 126 ; improving mac osx profile doc slightly

Issue 43 ; improving release notes and readme

Issue 146 ; adding explicit plugin versions, cleaning up maven 3.0-alpha warnings

Issue 43 ; updating release notes and readme for upcoming 1.3 release

Changed the Canvases to have preferred size rather than the Container.

Adding PSwing example to verify that Issue 25 has been fixed.

Making SWTGraphics2D not use internal .height field since isn't technically part of its public API; As per Issue 125. ...

Also, re-enabled the disabling of double buffering in the SWTBasicExample.

adding @since 1.3 tags

I agree completely. Comments of that kind are pretty useless, but instead of just mentioning it, why not fix it? ...

I disagree with having developer names in files at all. If we didn't have subversion to track contributions it'd make sense.

I totally disagree with a commenting style ...

/**
 * Returns the width of the line.
 * 
 * @return stroke width
 */
public float getLineWidth()

I prefer to not see my name in such source files.

More checkstyles on PSwing.

CheckStyle and final fixes.

Fixing CheckStyle warnings on PScrollpane. Including tabs, finals and missing javadocs.

issue#146 add personal info.

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

Fixed Issue 131

Cleaned up ExampleRunner a little. Seriously though, there's not much that can be done without abstracting the examples so much that they are too complicated to demonstrate what they are trying to show.

updating developer/contributor metadata, per emails rec'd

updating developer/contributor metadata, per emails rec'd

rolling back r865