updating maven plugin and maven report plugin versions

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

rolling back to r799, did not intend to commit

fixing javadoc warnings in core

more style and javadoc fixes

Fixing core CheckStyle warnings. All magic number warnings were on constant definitions. Cleaning them up would not have increased code clarity greatly enough to warrant it.

More CheckStyle blitzing on core. Javadocs are all there now. To drop the number much further I'll need to expand expressions for defining Property change codes, or break binary compatability by making constants final. I'm 100% for doing that, but I understand some people have reservations.

Removing FindBugs Excludes, since all they did was remove tests from the examples modules. Instead I removed the unnecessary reporting from examples. ...

Also, I've removed the umlgraph from the javadoc. It's useful, but it causes the build to complain loudly on windows machines.

Am not against putting something similar back in once we figure out how to make it play nicer.

Trying again with ignores rules.

Makind FindBugs ignore any Test classes and example classes.

Stabbing at some more CheckStyle complaints and making FileLength max=4000. We have PNode to thank for that.

Attacking some checkstyle complaints.

Additional Checkstyle fixes. Also, made java doc comments on private members/fields optional.

CheckStyle goodness

Attacking checkstyle complaints.

issue#110 - only whitespace and syntax. No semantic changes.

Issue 29 ; Added eclipse formatter configuration, tweaked checkstyle configuration to match, and ran eclipse formatter on the java source in core. Reduced checkstyle errors from 14037 to 2502. Note this commit contains formatting-related changes only, no code changes.

Issue 28; re-adding checkstyle plugin configuration to core, extras, and examples poms, adding sun_checks.xml to src/build/conf in each to enable check configuration