It looks like releng needs to be updated to use
eclipse-jarsigner-plugin.
Marc-Andre
./releng/org.eclipse.cdt.repo/pom.xml:40:
<artifactId>eclipse-signing-maven-plugin</artifactId>
Begin forwarded message:
Date: Wed, 14 Aug 2013 15:04:12 -0400
From: Thanh Ha <thanh.ha@xxxxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
<dash-dev@xxxxxxxxxxx> Subject: [cross-project-issues-dev]
Decommissioning of maven.eclipse.org
Hi Everyone,
Per bug 405750 [1] I'd like to take a look into decommissioning
maven.eclipse.org soon. We now have repo.eclipse.org and several
projects have already been publishing their artifacts there.
At the moment I'm aiming to do this at the end of this month around
September 30th 2013 but if this would be an issue for any projects
please let us know. As far as I can tell the only artifacts that seem
like they may affect any projects is 2 plugins from the dash project
which have not been deployed to repo.eclipse.org:
- eclipse-maven-signing-plugin
- eclipse-signing-maven-plugin
If your project uses either of these plugins this may affect you when
we take the server offline. The CBI project also provides a signing
plugin called the "eclipse-jarsigner-plugin" which is available on
repo.eclipse.org and I would recommend you switch to using this plugin
if this is the case. A README of how to use the plugin can be found
here [2].
Thanh
[1]
https://bugs.eclipse.org/405750
<
https://bugs.eclipse.org/bugs/show_bug.cgi?id=405750>
[2]
http://git.eclipse.org/c/cbi/org.eclipse.cbi.maven.plugins.git/tree/README
