2012/9/25 Olivier Lamy <[email protected]>: > 2012/9/25 Brett Porter <[email protected]>: >> I think we should ask first if central will sync from archiva-repository for >> selected group IDs to accommodate (we are still within their forge policy). >> >> Failing that, we should rsync the content into r.a.o to be picked up, rather >> than deploying to nexus. That's a lot of manual double-work (and not >> dogfooding would not be an option). > I have to verify but stage:copy should work with https as target repository.
Until it's fixed. I have merged the stage repo to https://archiva-repository.apache.org/archiva/repository/archiva-releases/ I will add this in ours poms and continue the release. I will be able later to put this content to apache nexus. BTW I'm not sure we need a central sync :-) we have a repo here https://archiva-repository.apache.org/archiva/repository/archiva-releases/ > >> >> - Brett >> >> On 25/09/2012, at 6:04 PM, Olivier Lamy <[email protected]> wrote: >> >>> Hi, >>> It looks rsync from >>> /www/people.apache.org/repo/m2-ibiblio-rsync-repository to maven >>> central is not anymore supported. (Don't ask me why I have some ideas >>> but I prefer to not discuss on the topic.....) >>> So if we want our release going to central we have deployed releases to >>> nexus. >>> I will created jira entry for that. >>> >>> >>> -- >>> Olivier Lamy >>> Talend: http://coders.talend.com >>> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> -- >> Brett Porter >> [email protected] >> http://brettporter.wordpress.com/ >> http://au.linkedin.com/in/brettporter >> http://twitter.com/brettporter >> >> >> >> >> > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy
