Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Question about signing and pack200

That plugin is working on a number of projects now.

and the sign command your talking about only does the sign I believe,
you have to pack prior to it and then again after it has been signed,
and then make sure the artifact.xml/jar are updated with checksums.

David Carver was going to promote the signing plugin somewhere today
so more people could get to it

these are some docs on its usage


jesse mcconnell

On Wed, May 18, 2011 at 00:44, Vincent Zurczak
<vincent.zurczak@xxxxxxxxxxxxxx> wrote:
> 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 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/
> 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 ] :
> --
> Vincent Zurczak
> R&D Engineer
> Petals Link - SOA open-source company
> +33 (0) 4 76 96 15 16
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx

Back to the top