Thanks, this is good feedback to know. I'm thinking maybe the best
option at the moment is to create a new server elsewhere thus leaving
maven.eclipse.org alone for now. Once the new server is ready to go we
can make the switch later.
Thanh
On 31/01/13 11:44 AM, Jesse McConnell wrote:
oh that is true, we use that plugin for our p2 repositories for jetty
as well so please leave that around for the time being
--
jesse mcconnell
jesse.mcconn...@gmail.com <mailto:jesse.mcconn...@gmail.com>
On Thu, Jan 31, 2013 at 10:41 AM, Matthias Sohn
<matthias.s...@gmail.com <mailto:matthias.s...@gmail.com>> wrote:
2013/1/31 Thanh Ha <thanh...@eclipse.org
<mailto:thanh...@eclipse.org>>
Hi Everyone,
Per Bug 394792 I'm looking at moving maven.eclipse.org
<http://maven.eclipse.org> to become a managed service at
Eclipse. I plan on tackling this issue soon and was wondering
if taking this server down would affect any projects?
the EGit project is downloading the eclipse-signing-maven-plugin
from maven.eclipse.org <http://maven.eclipse.org/>. So if you take
down this system
signing of our builds on Hudson would fail, this could be solved
if you can serve this plugin from a different place.
--
Matthias
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org <mailto:dash-dev@eclipse.org>
https://dev.eclipse.org/mailman/listinfo/dash-dev
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
