Looks like Dan actually got this set up a couple months ago while we were in the incubator.
I wrote a small patch http://gerrit.cloudera.org:8080/4118 to change our parent pom to the ASF parent. With this I was able to deploy a 1.0.0-SNAPSHOT to the ASF snapshots repo: https://repository.apache.org/content/repositories/snapshots/org/apache/kudu/ I also cherry-picked that patch on top of the 0.10.0 release tag and was able to stage the 0.10.0 repository here: https://repository.apache.org/content/repositories/orgapachekudu-1000/ Let's run a lazy consensus vote on the above staging repository - if someone else can try building against it and decides it looks good, I'll figure out how to "promote" this. Next steps would be to update our release documentation to include mvn deploys, and to set up a Jenkins job that auto-deploys snapshot builds on a nightly (or per-commit) basis. -Todd On Tue, Aug 23, 2016 at 1:11 PM, Mike Percy <mpe...@apache.org> wrote: > Woops, good catch. > > Mike > > > On Tue, Aug 23, 2016 at 12:01 PM, Todd Lipcon <t...@cloudera.com> wrote: > > > Hey folks > > > > Currently our pom is set up to deploy to Cloudera repos, but given that > we > > are an ASF project, we should be deploying to ASF maven. > > > > I filed https://issues.apache.org/jira/browse/INFRA-12479 to get us set > up > > in the ASF Nexus. Expect a gerrit review some time soon to change over > our > > pom, and then I'll figure out how to publish our most recent release(s). > > > > -Todd > > > -- Todd Lipcon Software Engineer, Cloudera
