Updating pom files to allow for next release to be based on Apache Maven publishing guidelines.
Review Request #3447 - Created Jan. 10, 2012 and submitted
Also updated the release version from 1.0.0-incubating to 1.1.0-incubating-SNAPSHOT
Ran full build with a clean local cache (rm -rf ~/.m2/repository/org/apache/flume).
Posted (Jan. 10, 2012, 7:57 p.m.)
Many of the child poms reference other project artifacts and specify the Flume version. It is a better practice to declare a variable in the parent pom that declares the Flume version. Then add a dependencyManagement section to the parent pom that defines all the Flume artifacts with their version. Finally, remove the version in each of the subproject so they will pick up the version from the managed dependency.