ISP-648 First draft of an opower-parent POM;  this version centralizes common maven plugin dependency setup and versioning (especially around the Java compiler behavior)
It leaves out surefire configuration and checkstyle configuration because Archmage and $R/pose-parent are pretty far apart on those right now
It centralizes (perhaps unnecessarily) our build resources which include the fact we often autopatch databases off db/patches directories
Finally, it institues a profile that will switch the java compiler version based on the compile-time discovery of the JDK - this is a crutch I'll tear down after we switch 100% over to Java 7
Per code review comment, moving the build and test resource block out of opower-parent because it's too proscriptive of the way child artifacts should deal with their resources.
Making the cobertura dependency of our maven-cobertura-plugin a property too
Merge pull request #1 from tvaughan77/master

ISP-648 First draft of an opower-parent POM;