| [cross-project-issues-dev] Question about signing and pack200 |
|
Hi, I'm not sure if this mailing-list is the place to ask this question, but I don't see a better one right now. SCA Tools has a build on Hudson based on Tycho. What I would like to do is to "promote" the last generated update site, meaning packing and signing it (manually for the moment). I logged in through SSH to build.eclipse.org and applied the "sign" command on the update site. Signing seems good but pack is not done. Instead, the logs include: Running Repack Sign on /shared/download-staging.priv/stp/out/temp_site_assembly_2.2.0.20110517171311.zip/plugins/org.eclipse.soa.sca.sca1_0.model_2.2.0.201105171710.jar I had understood "sign" would also pack. By default, it is not done in our build and there is no pack.gz after the signing. Should I do something more specific for pack? Thanks for any help, Vincent. PS: I also plan to script the signing thanks to this Maven plugin [0] as soon as it is released. [ 0 ] : https://bugs.eclipse.org/bugs/show_bug.cgi?id=342336 --
Vincent Zurczak R&D Engineer Petals Link - SOA open-source company http://vzurczak.wordpress.com +33 (0) 4 76 96 15 16 |