so do I have to invoke the site.p2 action in advance? I think I've tried that with the result that the jars in the site have been
signed but not those in the webstart folder (as result of create.eclipse.jnlp.product).

Or can I add that (and how) as a prerequisite to the create.eclipse.jnlp.product action?

I'm afraid that the signing capabilities are especially tailored to be used with the site.p2 action (it's also
intertwined with the pack200 code). It was never intended to work with the JNLP stuff. So I'm afraid you'll need to
revert to some copy/pasting and write your own signing for that.

- thomas

On 02/01/2012 10:22 AM, Henrik Rentz-Reichert wrote:
> Hi Thomas,
>
> so do I have to invoke the site.p2 action in advance? I think I've tried that with the result that the jars in the site have been
> signed but not those in the webstart folder (as result of create.eclipse.jnlp.product).
>
> Or can I add that (and how) as a prerequisite to the create.eclipse.jnlp.product action?
>
> Thanks,
> Henrik
>
>
> Am 01.02.2012 09:54, schrieb Thomas Hallgren:
>> Hi Henrik,
>>
>> The signing functionality is part of the 'site.p2' action. I don't think it is included as a prerequisite to the
>> create.eclipse.jnlp.product.
>>
>> - thomas
>>
>>
>>
>> On 01/31/2012 03:14 PM, Henrik Rentz-Reichert wrote:
>>> Hi,
>>>
>>> I want to build a web start Eclipse application using Buckminster in a Hudson build.
>>>
>>> I have created a wrapping feature for this purpose.
>>> Inside this feature I've created an extension spec (xspec).
>>> The relevant part is:
>>>
>>> <actions>
>>> <public name="create.eclipse.jnlp.product" actor="ant">
>>> <actorProperties>
>>> <property key="buildFileId" value="buckminster.pdetasks"/>
>>> <property key="targets" value="create.eclipse.jnlp.product"/>
>>> </actorProperties>
>>> <properties>
>>> <property key="buckminster.eclipse.productFile"
>>> value="org.eclipse.platform.ide"/>
>>> <property key="buckminster.eclipse.deleteuilauncher" value="false"/>
>>> </properties>
>>> <prerequisites alias="action.requirements">
>>> <attribute name="feature.exports"/>
>>> </prerequisites>
>>> <products alias="action.output" base="${buckminster.output}">
>>> <path path="webstart/"/>
>>> </products>
>>> </public>
>>> </actions>
>>>
>>> Then I perform this action in the build with the following properties:
>>>
>>> site.signing=true
>>> site.retain.unpacked=true
>>> signing.type=local
>>> local.keystore.path=D:/hudson/keystore/keystore.jks
>>> local.keystore.alias=xxx
>>> local.keystore.password=xxx
>>>
>>> So far the build works quite well and in the buckminster.output I find a folder for my wrapping feature containing a webstart
>>> folder with plugins, features and jnlp files.
>>>
>>> Unfortunately the jars aren't signed!
>>>
>>> Can anybody help?
>>>
>>> Thanks,
>>> Henrik
>>
>