I was looking at
https://cwiki.apache.org/confluence/display/FLUME/How+to+Release and noticed
that it doesn't document deploying artifacts to the Apache Nexus repository. In
fact, it looks like the 1.1 release was never finished as the artifacts can't
be found in Maven Central. This is critical for anyone wanting to extend Flume
with their own components so I would ask that this please be added as a step to
the release process.
I am curious though why the process doesn't use the Maven Release plugin as it
appears the project is set up for it to work. That would remove a number of the
manual steps that have to take place.
Also, I noticed in the parent pom that all the flume artifacts are declared
with a specific version. Is there a reason that ${project.version} wasn't used
instead? This would save the release manager from ever having to edit them.
Ralph
