Skip to main content

[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))

From this page: http://central.sonatype.org/pages/producers.html, it sounds like Eclipse could get a free license from Sonatype for the integration.  That page also notes that other 'forges' like Apache, JBoss, and Oracle are already connected.

I don't know how Eclipse's repos are viewed.  For the LocationTech working group, users have to go to extra work to include/use the LocationTech Nexus.  From my point of view, publishing project artifacts to Maven central is much more desirable since it eases adoption.

To some degree, I'd have to the reverse opinion:  Why is Eclipse going to the trouble of maintaining servers that our projects' users have to opt into working with?


On 11/10/2017 04:55 AM, Mickael Istria wrote:


On Fri, Nov 10, 2017 at 10:19 AM, Mikaël Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx> wrote:
AFAICT, none.
[...]
oops, hit send too fast. 

:D
Those kind of answer says a lot about how your deep opinion on this question ;)

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.

Ok.
What would be interesting would be to have some metrics about the uptime (with "up" meaning working as expected) of the current Nexus recently, to have some metrics evaluating the "annoyance" caused by current Nexus (eg: Nexus made projects not build-able N hours per months). Ideally, those could be shown on https://status.eclipse.org/ .
I have the impression that this uptime is now good, and Nexus is not any more an issue these days.

So far, I still don't feel convinced that the Nexus Pro cost and effort is worth it for our community; so unless the metrics suggested above or some new arguments change my mind, it's not an idea I would bring nor fully support at the Board.
--
Mickael Istria
Eclipse IDE developer, at Red Hat Developers community
Elected Committer Representative at the Eclipse Foundation board of director


_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council

IMPORTANT: 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.



Back to the top