Hi, On Fri, Jun 22, 2012 at 6:32 AM, Ralph Goers <[email protected]>wrote:
> 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. > Agreed. Since Mike is the RM for 1.2.0 release, I would request him to update this page with the relevant details. > > 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. > Although I like the release plugin a lot, there is a concern with respect how well it fits with the typical release process. For instance, how would you create a release candidate build with the plugin? If you do then it will change the version identifiers and also create RC specific tags. Further, when a release candidate is approved, you would have to run the release plugin again to change the version from RC to release version - which requires code changes and new tag creation. That said, there are work arounds for this such as using the release version for the release candidate and then updating the tags as more RCs are spun. I am not too sure if that is the right thing to do either. Any suggestions on getting this going are welcome. > > 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. > I believe that all of these versions are only in the parent pom. Therefore a simple find/replace should suffice. Regards, Arvind Prabhakar > > Ralph
