|
Re: Selective signing [message #546314 is a reply to message #546286] |
Mon, 12 July 2010 12:57 |
Henrik Lindberg Messages: 2509 Registered: July 2009 |
Senior Member |
|
|
Hi,
Perhaps not the best way, but you could perhaps do this:
- create your site with only your things (all signed)
- use the b3 aggregator to set up a repository that you create the
product against, and that you can use as the update site.
- the repository you create can be a composite site pointing to your
built site and Eclipse Helios for instance.
- henrik
On 7/12/10 1:40 PM, Carsten Reckord wrote:
> Hi all,
>
> I'm trying to get signing set up for our update site. I have the signing
> process itself running fine already. But now I'm facing the problem that
> the site contains some org.eclipse.* artifacts that of course I don't
> want to sign.
>
> So is there a way to selectively sign just a part of the site?
>
> I already tried excluding the eclipse artifacts from the site in the
> first place (I don't really need them there, so that would have been a
> plus). But I failed because that left the products on the site broken
> and unlaunchable: We have org.eclipse.rcp, the org.eclipse.ecf stuff and
> a few others included in our product feature. I tried excluding them
> from the site by adapting the bundle.jars and feature.jars groups, which
> worked fine as far as site contents were concerned. However that seems
> to fry the product because afterwards it fails to launch because of a
> missing org.eclipse.core.runtime (which gets installed from anotehr
> site, but there seems to be something wrong with the product's
> config.ini and related config files)
>
>
> Best regards,
> Carsten
|
|
|
Re: Selective signing [message #546359 is a reply to message #546314] |
Mon, 12 July 2010 14:26 |
Carsten Reckord Messages: 139 Registered: July 2009 |
Senior Member |
|
|
Hi Henrik,
On 12.07.2010 14:57, Henrik Lindberg wrote:
> Hi,
> Perhaps not the best way, but you could perhaps do this:
> - create your site with only your things (all signed)
> - use the b3 aggregator to set up a repository that you create the
> product against, and that you can use as the update site.
I assume with "create the product" you mean the installation step, i.e. pulling the jars from the site and installing them using director?
In that case the problem still exists, because it appears that it's not the installation step that messes up the product, but the metadata
generated by the p2SiteGenerator in the site.p2 step.
I could just completely exclude the feature that defines our product from the site, however we'd prefer to have the product feature and
launchers on the site...
> - the repository you create can be a composite site pointing to your
> built site and Eclipse Helios for instance.
>
> - henrik
>
> On 7/12/10 1:40 PM, Carsten Reckord wrote:
>> Hi all,
>>
>> I'm trying to get signing set up for our update site. I have the signing
>> process itself running fine already. But now I'm facing the problem that
>> the site contains some org.eclipse.* artifacts that of course I don't
>> want to sign.
>>
>> So is there a way to selectively sign just a part of the site?
>>
>> I already tried excluding the eclipse artifacts from the site in the
>> first place (I don't really need them there, so that would have been a
>> plus). But I failed because that left the products on the site broken
>> and unlaunchable: We have org.eclipse.rcp, the org.eclipse.ecf stuff and
>> a few others included in our product feature. I tried excluding them
>> from the site by adapting the bundle.jars and feature.jars groups, which
>> worked fine as far as site contents were concerned. However that seems
>> to fry the product because afterwards it fails to launch because of a
>> missing org.eclipse.core.runtime (which gets installed from anotehr
>> site, but there seems to be something wrong with the product's
>> config.ini and related config files)
>>
>>
>> Best regards,
>> Carsten
>
|
|
|
Re: Selective signing [message #546372 is a reply to message #546359] |
Mon, 12 July 2010 15:04 |
Henrik Lindberg Messages: 2509 Registered: July 2009 |
Senior Member |
|
|
On 7/12/10 4:26 PM, Carsten Reckord wrote:
> Hi Henrik,
>
> On 12.07.2010 14:57, Henrik Lindberg wrote:
>> Hi,
>> Perhaps not the best way, but you could perhaps do this:
>> - create your site with only your things (all signed)
>> - use the b3 aggregator to set up a repository that you create the
>> product against, and that you can use as the update site.
>
> I assume with "create the product" you mean the installation step, i.e.
> pulling the jars from the site and installing them using director?
yes.
> In that case the problem still exists, because it appears that it's not
> the installation step that messes up the product, but the metadata
> generated by the p2SiteGenerator in the site.p2 step.
>
That is bad. I believe we do publish Buckminster products that are
signed this way - but I need Thomas to verify (don't know if he is back
from vacation yet).
- henrik
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04173 seconds