Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355519 - eclipse-signing-maven-plugin 1.0.2 seems to not sign properly
Summary: eclipse-signing-maven-plugin 1.0.2 seems to not sign properly
Status: CLOSED INVALID
Alias: None
Product: Dash
Classification: Technology
Component: Maven (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Dash Incoming bugs CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-23 10:46 EDT by Matthias Sohn CLA
Modified: 2011-08-23 19:51 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Sohn CLA 2011-08-23 10:46:54 EDT 
Since we switched the EGit build to use 

<groupId>org.eclipse.dash.maven</groupId>
<artifactId>eclipse-signing-maven-plugin</artifactId>
<version>1.0.2</version>

the build log still looks like signing works :
https://hudson.eclipse.org/hudson/job/egit/1640/consoleFull
(search for "signing" in the browser)

but when installing EGit from the resulting p2 repository at
http://download.eclipse.org/egit/updates-nightly
I am asked if I am ok to install unsigned software and also
"About Eclipse > Installation Details > Plug-ins" shows that
the egit and jgit plugins are not signed.
Comment 1 Chris Aniszczyk CLA 2011-08-23 10:49:25 EDT 
Are you sure p2 hasn't cached anything on your end?
Comment 2 Matthias Sohn CLA 2011-08-23 19:42:50 EDT 
I'll retry with a fresh installation
Comment 3 Matthias Sohn CLA 2011-08-23 19:51:20 EDT 
bingo, everything worked fine when installing into a fresh package so it seems it was caused by p2 caching vodoo