[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cross-project-issues-dev] Which moment of the build i should call the sign
|
The "waitForChangedAttibs"
task is to make the signing synchronous
... well, at least synchronous in effect, since the build will wait for
the attributes to change, before continuing with the rest of the build.
And, yes, best place is before you call the
unpackUpdateJars.
HTH
From:
| "Paula Gustavo-WGP010" <wgp010@xxxxxxxxxxxx>
|
To:
| <cross-project-issues-dev@xxxxxxxxxxx>
|
Date:
| 09/25/2008 03:49 PM
|
Subject:
| [cross-project-issues-dev] Which moment
of the build i should call the sign |
Hi,
I'm working right now to add the feature &
plugins signing to DSDP.MTJ build. I looked at a lot of documentation about
how to call the sign scripts, but it is not clear to me yet in which step
of the build process a should call a the signing script.
currently we call pde to generate the update
site and after that we use unpackUpdateJars to generate the final package
that we copy to the download site.
it seems that the best place is before we
call the unpackUpdateJars, since in that way both the update site jars
and the final jars on the download site will be signed. the problem is
that it seems that the sign script is asynchronous so i don't know how
to do it on an ant script. (i saw http://wiki.eclipse.org/Platform-releng-signedbuild,
but i didn't understood how to use waitForChangedAttribs target that waits
for the sign to finish).
If i call it afar all build is finished, is
the idea to sign update site features/ plugins and then re-generate the
final zip based on it?
Can someone help me with that?
Thanks
gustavo _______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev