| P2 generator fails to generate config iu [message #120388] |
Fri, 31 October 2008 06:53  |
Eclipse User |
|
|
|
Hello!
I am currently setting up a headless build of an eclipse Product based on
Features. I am almost there, but I have a problem when it comes to
generate the metadata for the product.
I followed the instructions in the eclipse help and several other
tutorials, but now im am totally stuck:
When i export the product in w32, everything goes as expected. My metadata
is generated, i can install the product and update, etc...
Now i did a headless product export on linux/x86 and as far as i can see
everithing works well except that a unit is not being generated in the
content.xml.
In the exported metadata on windows, i got this:
<unit id='toolingch.inteco.scout.product.config.win32.win32.x86'
version='1.0.0'>
<provides size='2'>
<provided namespace='org.eclipse.equinox.p2.iu'
name='toolingmy.product.config.win32.win32.x86' version='1.0.0'/>
<provided namespace='toolingmy.product'
name='my.product.config' version='1.0.0'/>
</provides>
<filter>
( & (osgi.ws=win32) (osgi.os=win32) (osgi.arch=x86))
</filter>
<touchpoint id='org.eclipse.equinox.p2.osgi'
name='toolingmy.product.config.win32.win32.x86' version='1.0.0'/>
<touchpointData size='1'>
<instructions size='2'>
<instruction key='unconfigure'>
setProgramProperty(propName:osgi.splashPath,
propValue:);setProgramProperty(propName:eclipse.product, propValue:);
</instruction>
<instruction key='configure'>
setProgramProperty(propName:osgi.splashPath,
propValue:platform:/base/plugins/ch.inteco.scout);setProgram Property(propName:eclipse.product,
propValue:my.product);
</instruction>
</instructions>
</touchpointData>
</unit>
When i do the export on linux, this unit is missing. Of course, when
installing, this dependency cannot be satisfied.
I added this section by hand, and after that, everything goes well.
If you need any additional information, feel free to ask!
Am i doing something wrong?
Thanks for your help in advance.
|
|
|
| Re: P2 generator fails to generate config iu [message #121198 is a reply to message #120388] |
Fri, 14 November 2008 03:45  |
| Eclipse User |
|
|
|
Hallo Timo,
I seem to have the same problem (see my post from 13.11.).
Have you come any further?
Regards
Alexander
"Timo Schmid" <timo.schmid@gmail.com> schrieb im Newsbeitrag
news:38a5d8c0b779ab9c25f8853a225c1b37$1@www.eclipse.org...
> Hello!
>
> I am currently setting up a headless build of an eclipse Product based on
> Features. I am almost there, but I have a problem when it comes to
> generate the metadata for the product.
> I followed the instructions in the eclipse help and several other
> tutorials, but now im am totally stuck:
>
> When i export the product in w32, everything goes as expected. My metadata
> is generated, i can install the product and update, etc...
>
> Now i did a headless product export on linux/x86 and as far as i can see
> everithing works well except that a unit is not being generated in the
> content.xml.
>
> In the exported metadata on windows, i got this:
>
> <unit id='toolingch.inteco.scout.product.config.win32.win32.x86'
> version='1.0.0'>
> <provides size='2'>
> <provided namespace='org.eclipse.equinox.p2.iu'
> name='toolingmy.product.config.win32.win32.x86' version='1.0.0'/>
> <provided namespace='toolingmy.product'
> name='my.product.config' version='1.0.0'/>
> </provides>
> <filter>
> ( & (osgi.ws=win32) (osgi.os=win32) (osgi.arch=x86))
> </filter>
> <touchpoint id='org.eclipse.equinox.p2.osgi'
> name='toolingmy.product.config.win32.win32.x86' version='1.0.0'/>
> <touchpointData size='1'>
> <instructions size='2'>
> <instruction key='unconfigure'>
> setProgramProperty(propName:osgi.splashPath,
> propValue:);setProgramProperty(propName:eclipse.product, propValue:);
> </instruction>
> <instruction key='configure'>
> setProgramProperty(propName:osgi.splashPath,
> propValue:platform:/base/plugins/ch.inteco.scout);setProgram Property(propName:eclipse.product,
> propValue:my.product);
> </instruction>
> </instructions>
> </touchpointData>
> </unit>
>
> When i do the export on linux, this unit is missing. Of course, when
> installing, this dependency cannot be satisfied. I added this section by
> hand, and after that, everything goes well.
>
> If you need any additional information, feel free to ask!
> Am i doing something wrong?
>
> Thanks for your help in advance.
>
|
|
|
Powered by
FUDForum. Page generated in 0.04032 seconds
Home