[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse.org-architecture-council] Why Nexus Pro then? (was Maven Central (was Re: Nov 9 Minutes))
|
| oops, hit send too fast.
However, Nexus is not only used for repository hosting, it is also used as a maven central proxy for Eclipse projects. As we've experienced some months ago, when repo.eclipse.org goes down, all projects builds are failing. Nexus Pro has some HA capabilities that the OSS version does not. This is where Nexus Pro would be interesting, at least from an infra point of view.
Cheers,
--
Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 🐦 @mikbarbero
AFAICT, none.
Hi all,
Thanks for the answers on the thread about OSSHR and Eclipse.org (working well together). So now I've got to ask the main question: do we really need a Nexus Pro at Eclipse.org if current Nexus is fine for snapshots, and OSSRH is fine for releases and Maven Central? What important workflows would it cover that aren't covered by Nexus community + OSSHR?
Those are important questions that need to have a good answer before we can expect the Foundation Board to approve or even discuss adoption of Nexus Pro in more details.
Cheers,
_______________________________________________ eclipse.org-architecture-council mailing list eclipse.org-architecture-council@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-councilIMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
|
Attachment:
signature.asc
Description: Message signed with OpenPGP
