Closes #113 Adding required Sonatype OSS properties to poms to allow for...

... release
On https://oss.sonatype.org/, if you do a search for fluo, you will see that I've deployed snapshot artifacts. I did this using the 'release' profile last night to make sure the proper artifacts were being published. Snapshots, however, do not require source jars and javadocs but I did verify they were being built, nonetheless.

I also ran with a 'release:prepare' last night so that the artifacts would go into staging and the release procedures would be executed. Sonatype runs the final artifacts through a verification to show that the poms have the required fields, the artifacts are signed, the crcs match, and that the source/javadoc jars are included. The verification passed but i stopped the build before it created the remote tag. I also did not actually do the "release:perform" which actually commits the new release version to the remote repository and updates the next version to snapshot.