PDE Product Build using existing config.ini [message #17982] |
Wed, 27 August 2008 11:11  |
Eclipse User |
|
|
|
I having some trouble getting the PDE headless build to use an existing
'config.ini', instead it generates a default one. I have created a product
configuration and invoke the productBuild.xml via AntRunner. The entire
build process works without errros. However, the final product output does
not contain the custom 'config.ini'
I'm using Eclipse 3.4 Ganymede as my IDE and headless build environment.
The following is an excerpt from my .product definition:
<configIni use="default">
<linux>/features/org.sample.feature/configuration/config.ini </linux>
<macosx>/features/org.sample.feature/configuration/config.ini </macosx>
<solaris>/features/org.sample.feature/configuration/config.ini </solaris>
<win32>/features/org.sample.feature/configuration/config.ini </win32>
</configIni>
Any ideas on how to resolve this would be appreciated.
|
|
|
Re: PDE Product Build using existing config.ini [message #18700 is a reply to message #17982] |
Sat, 30 August 2008 12:07  |
Eclipse User |
|
|
|
Hi Dennis,
Just noticed this looking for something else.
Mine looks like this and works when using the Export Product wizard.
<configIni use="default">
<linux>/com.wwm.webservice.feature/config.ini</linux>
<macosx>/com.wwm.webservice.feature/config.ini</macosx>
<solaris>/com.wwm.webservice.feature/config.ini</solaris>
<win32>/com.wwm.webservice.feature/config.ini</win32>
</configIni>
In my case, the config.ini is in the same project as my .product file.
Cheers,
Neale
Dennis O'Flynn wrote:
> I having some trouble getting the PDE headless build to use an existing
> 'config.ini', instead it generates a default one. I have created a product
> configuration and invoke the productBuild.xml via AntRunner. The entire
> build process works without errros. However, the final product output does
> not contain the custom 'config.ini'
>
>
>
> I'm using Eclipse 3.4 Ganymede as my IDE and headless build environment.
>
>
>
> The following is an excerpt from my .product definition:
>
> <configIni use="default">
>
> <linux>/features/org.sample.feature/configuration/config.ini </linux>
>
> <macosx>/features/org.sample.feature/configuration/config.ini </macosx>
>
> <solaris>/features/org.sample.feature/configuration/config.ini </solaris>
>
> <win32>/features/org.sample.feature/configuration/config.ini </win32>
>
> </configIni>
>
>
>
>
>
> Any ideas on how to resolve this would be appreciated.
>
>
|
|
|
Re: PDE Product Build using existing config.ini [message #577907 is a reply to message #17982] |
Sat, 30 August 2008 12:07  |
Eclipse User |
|
|
|
Hi Dennis,
Just noticed this looking for something else.
Mine looks like this and works when using the Export Product wizard.
<configIni use="default">
<linux>/com.wwm.webservice.feature/config.ini</linux>
<macosx>/com.wwm.webservice.feature/config.ini</macosx>
<solaris>/com.wwm.webservice.feature/config.ini</solaris>
<win32>/com.wwm.webservice.feature/config.ini</win32>
</configIni>
In my case, the config.ini is in the same project as my .product file.
Cheers,
Neale
Dennis O'Flynn wrote:
> I having some trouble getting the PDE headless build to use an existing
> 'config.ini', instead it generates a default one. I have created a product
> configuration and invoke the productBuild.xml via AntRunner. The entire
> build process works without errros. However, the final product output does
> not contain the custom 'config.ini'
>
>
>
> I'm using Eclipse 3.4 Ganymede as my IDE and headless build environment.
>
>
>
> The following is an excerpt from my .product definition:
>
> <configIni use="default">
>
> <linux>/features/org.sample.feature/configuration/config.ini </linux>
>
> <macosx>/features/org.sample.feature/configuration/config.ini </macosx>
>
> <solaris>/features/org.sample.feature/configuration/config.ini </solaris>
>
> <win32>/features/org.sample.feature/configuration/config.ini </win32>
>
> </configIni>
>
>
>
>
>
> Any ideas on how to resolve this would be appreciated.
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.07017 seconds