If you look at https://repository.apache.org/#stagingRepositories, I see an open repo for toree. You need to select it and hit "Close" I believe to publish to staging. On close, it will provide a maven repo url that someone else can use as a repo url for trying it out. After the final vote, the repo will need to be "released"
thanks -- Hitesh On Fri, Jan 6, 2017 at 12:09 PM, Chip Senkbeil <[email protected]> wrote: > I just published 0.1.0 artifacts to staging in preparation for an RC4 vote. > I cannot tell where they have gone to include a link in the description. > > The root of the staging deployment is here: > https://repository.apache.org/service/local/staging/deploy/ > maven2/org/apache/toree/ > > And I see successfully publish messages including "published > toree-kernel_2.10 to > https://repository.apache.org/service/local/staging/deploy/ > maven2/org/apache/toree/toree-kernel_2.10/0.1.0-incubating/ > toree-kernel_2.10-0.1.0-incubating.jar > " > > When I visit the root of the deployment, I see "Staging of Repository > within profile ID='1285d3cb661df6' is not yet started!". And I don't see > anything under the Nexus staging listing for Apache Toree under > https://repository.apache.org#view-repositories;staging~browsestorage > > Did I miss a step with getting the artifacts into staging? And, for > staging, should the artifacts have an RC4 appended to them? Or is it okay > for me to overwrite staging with a new 0.1.0 artifact until we have the > final RC? >
