On 15 October 2013 17:53, Matt Benson <gudnabr...@gmail.com> wrote: > Just because dist.a.o is the canonical place for the source release to live > does not necessarily mean that the artifact cannot be deployed to Nexus. > We do have the option to let Maven upload everything to Nexus, vote on the > artifacts, and then copy the successfully-voted-on source artifact to > dist.a.o.
Which is what I thought I expressed here: > AFAIK the only choice is: > + to use Nexus for both Maven and ASF artifacts > + or use Nexus for Maven and the SVN dist/dev tree for ASF artifacts Though I now realise I did not make it clear that I was referring to the staging of release artifacts. > Matt > > > On Tue, Oct 15, 2013 at 11:27 AM, sebb <seb...@gmail.com> wrote: > >> On 14 October 2013 01:51, Gary Gregory <garydgreg...@gmail.com> wrote: >> > On Sun, Oct 13, 2013 at 7:51 PM, sebb <seb...@gmail.com> wrote: >> >> On 12 October 2013 09:08, Olivier Lamy <ol...@apache.org> wrote: >> >>> why not having those files deployed? >> >> >> >> See my reply in another thread. >> >> The Maven project deploys these to Maven Central. >> >> >> >> The primary release channel for the bin and src tarballs must be the >> >> ASF mirror system, not Maven Central (MC). >> >> Does this mean that we cannot publish to MC as well? I don't know. >> > >> > It would make my life easier if every thing was published to one >> > place. MC is good because Maven and Ivy know how to resolve to those. >> >> ASF releases must be via the ASF mirrors; Maven jars must be to a Maven >> repo. >> It's not possible to publish to a single place. >> >> > No one tools know how to resolve to Apache "dist" or whatnot. >> >> Not sure I follow what you mean here. >> >> > I understand that we have to publish to an Apache location, but maybe >> > there is a way to make it easier. >> >> AFAIK the only choice is: >> + to use Nexus for both Maven and ASF artifacts >> + or use Nexus for Maven and the SVN dist/dev tree for ASF artifacts >> >> > Gary >> >> >> >>> On 11 October 2013 23:21, Emmanuel Bourg <ebo...@apache.org> wrote: >> >>>> The parent pom currently attaches the -bin and -src archives to the >> >>>> deploy phase, which means we have to delete them manually in Nexus. >> >>>> >> >>>> Can we agree to change that? >> >>>> >> >>>> Emmanuel Bourg >> >>>> >> >>>> >> >>>> --------------------------------------------------------------------- >> >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> >>>> For additional commands, e-mail: dev-h...@commons.apache.org >> >>>> >> >>> >> >>> >> >>> >> >>> -- >> >>> Olivier Lamy >> >>> Ecetera: http://ecetera.com.au >> >>> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >>> >> >>> --------------------------------------------------------------------- >> >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> >>> For additional commands, e-mail: dev-h...@commons.apache.org >> >>> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> >> > >> > >> > >> > -- >> > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org >> > Java Persistence with Hibernate, Second Edition >> > JUnit in Action, Second Edition >> > Spring Batch in Action >> > Blog: http://garygregory.wordpress.com >> > Home: http://garygregory.com/ >> > Tweet! http://twitter.com/GaryGregory >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> > For additional commands, e-mail: dev-h...@commons.apache.org >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
