Am 09.12.2011 07:13, schrieb Igor Fedorenko: > I honestly think you are overreacting. oss.sonatype.org is just an > artifact repository, a file server essentially.
Vendor neutrality is important. Why isn't it possible to publish to download.eclipse.org (or whatever.eclipse.org) and then mirror the bits you need? Becoming a mirror is dead easy. http://www.eclipse.org/downloads/mir_request.php > Third, maven.eclipse.org has to be officially supported part of eclipse > infrastructure and treated the same way as download.eclipse.org from > availability and reliability point of view. >From what I've heard, Maven/Tycho will play an important role in the coming common build infrastructure. Thus, I think that it may be possible to support that system like Hudson. > Things like 365727 [1] simply should not happen. Frankly, I don't really see who is too blame for the issue. It could very likely be a bug in the software being used. It could also be a user error. In any case, you certainly can't expect that such issues won't happen even if you hire dedicated server operators. > Fourth, Eclipse Foundation needs to decide if maven.eclipse.org should > be synced to the Central repository or not and negotiate with Sonatype > conditions and procedures if the sync is desired. That confuses me a bit. Anybody is free to setup an Eclipse mirror at their will. No negotiation is necessary. Can't Sonatype just mirror maven.eclipse.org as others mirror download.eclipse.org? I'm pretty sure Denis is willing to allow rsync from maven.eclipse.org as well. -Gunnar -- Gunnar Wagenknecht [email protected] http://wagenknecht.org/ _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
