Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] p2 repositories and eclipse.org signing

Konstantin,

You can to use the p2.process.artifacts  task to update the MD5 signatures of the bundles in your repo once they've been signed

In our build, we run it like this which updates the checksums and also creates packed files in the repo

<p2.process.artifacts repositoryPath="file://${yourrepo}" pack="true" />

http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_repositorytasks.htm

Kim






From:        "Konstantin Komissarchik" <konstantin.komissarchik@xxxxxxxxxx>
To:        "'Cross project issues'" <cross-project-issues-dev@xxxxxxxxxxx>
Date:        01/06/2011 03:39 PM
Subject:        [cross-project-issues-dev] p2 repositories and eclipse.org signing
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx




I’d like to hear how people handle signing of p2 repositories. My project build produces a p2 repository archive. For my first attempt, I used eclipse.org sign script to sign the repository… Oops… The p2 repository is now corrupted. Understandable in retrospect. Signing changes the plugin and feature jars. The checksums stored in p2 metadata no longer match.
 
So, it seems that one must perform signing in the middle of the build process running on Hudson. How would I do this given the convoluted signing infrastructure we have to use?
 
- Konstantin_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


Back to the top