Thanks Ralph - that makes sense. Once the nexus repository for Flume is setup, I will try doing the manual deployment.
Arvind On Tue, Jan 10, 2012 at 4:25 AM, Ralph Goers <[email protected]> wrote: > I pointed out the problem with not extending the Apache POM during the > release. Since it is not mandatory it was not a blocker. > > I believe you should be able to deploy the artifacts to the staging repo > using mvn deploy:deploy-file. However, you first need to have the repository > set up to accept Flume artifacts. > > For the next release I would suggest extending the Apache parent pom, trying > to do the release with the Maven release plugin, and get mvn site to do > something useful. > > Ralph > > On Jan 10, 2012, at 12:18 AM, Arvind Prabhakar wrote: > >> Hi Ralph, >> >> I just looked at the release tag and realized that the flume top-level >> pom does not extend out of the Apache parent pom - something that is >> apparently needed to host the release artifacts in maven central. >> There seem to be other issues too (like the release being cut locally >> already) which make it hard for me to figure out how best to go about >> deploying these artifacts to the central repo. >> >> I have therefore filed INFRA-4307 requesting infrastructure's >> assistance in deploying these artifacts. >> >> Hopefully we will have it resolved soon. My apologies for the delay in >> getting through this. >> >> Thanks, >> Arvind >> >> >> On Sat, Jan 7, 2012 at 9:15 PM, Ralph Goers <[email protected]> >> wrote: >>> Eric, I'm just wondering when you will be finishing the release and >>> publishing these artifacts. Anyone trying to build the Flume NG Appender >>> support in Log4j 2 is going to fail until they are. >>> >>> Ralph >>> >>> On Jan 5, 2012, at 10:41 AM, Karthik K wrote: >>> >>>> Great. >>>> >>>> By any chance, are there maven artifacts published for the same ? >>>> >>>> Also from a code maintenance perspective, if 1.0.x is not production grade >>>> yet, would there by future releases / development on the flum 0.90.x >>>> codeline until the transition is complete ? >>>> >>>> -- >>>> Karthik. >>>> >>>> >>>> On Wed, Jan 4, 2012 at 11:05 PM, Eric Sammer <[email protected]> wrote: >>>> >>>>> All: >>>>> >>>>> I'm incredibly excited to announce that Apache Flume 1.0.0-incubating has >>>>> been released and is now available for download! >>>>> >>>>> Download and signature: >>>>> >>>>> http://www.apache.org/dyn/closer.cgi/incubator/flume/flume-1.0.0-incubating/flume-1.0.0-incubating.tar.gz >>>>> >>>>> http://www.apache.org/dist/incubator/flume/flume-1.0.0-incubating/flume-1.0.0-incubating.tar.gz.asc >>>>> >>>>> Checksums: >>>>> >>>>> http://www.apache.org/dist/incubator/flume/flume-1.0.0-incubating/flume-1.0.0-incubating.tar.gz.md5 >>>>> >>>>> http://www.apache.org/dist/incubator/flume/flume-1.0.0-incubating/flume-1.0.0-incubating.tar.gz.sha1 >>>>> >>>>> Apache Flume Committers' keys: >>>>> http://www.apache.org/dyn/closer.cgi/incubator/flume/KEYS >>>>> >>>>> Getting started: >>>>> https://cwiki.apache.org/confluence/display/FLUME/Getting+Started >>>>> >>>>> File JIRAs: >>>>> http://issues.apache.org/jira/browse/FLUME >>>>> >>>>> Note that 1.0.0-incubating is a significant milestone for a few reasons. >>>>> * Our first release since moving into the incubator and within the Apache >>>>> Software Foundation >>>>> * It's the first release of "Flume NG" (which we can now just call 1.0.0). >>>>> * It's 1.0.0! >>>>> >>>>> As the release notes say, this is Flume "NG" and is significantly >>>>> different >>>>> than Flume "OG" or the 0.9.x branch that has been previously released. We >>>>> consider this to be of alpha quality and not intended for full reliable >>>>> production quality data delivery. All APIs should be consider flexible. >>>>> >>>>> A huge thanks to all contributors (coders, testers, feedback-givers, and >>>>> users) and our mentors for guiding us through the first (only slightly >>>>> painful) release! >>>>> -- >>>>> Eric Sammer >>>>> twitter: esammer >>>>> data: www.cloudera.com >>>>> >>> >
