Eclipse Community Forums: Rich Client Platform (RCP) » Headless Build - customized config.ini is not delivered by automated headless build!

Home » Eclipse Projects » Rich Client Platform (RCP) » Headless Build - customized config.ini is not delivered by automated headless build!

Show: Today's Messages :: Show Polls :: Message Navigator

Headless Build - customized config.ini is not delivered by automated headless build! [message #465496]

Fri, 30 March 2007 09:38

Robert Reinhardt

Messages: 7
Registered: July 2009

Junior Member

Hi,

Some weeks ago we have successfully introduced a headless automated
build for our rcp application.
The build is working on our locale dev-environments (using eclipse 3.2.1
as ide & targetplattform on Win2K) and on our build server(Sun Solaris
on a HPUx).

Now he have introduced a shared configuration site that is configured
via our customized config.ini file.
In the launch config of the product at the Configuration/Configuration
File section the option "Use an existing confing.ini as default template"
The config.ini is located in our main feature and is located at a
root/configuration folder that copies all files to a
runtime/configuration folder during local build.
The config.ini is stored in the cvs. The product that is refered by the
build.properties refers to our customized config.ini.

Our problem:
At starting the headless build on our local machines everything works
fine and the customized confing.ini is included in the builded client,
but atstarting the headless build on our build server(sun solaris on
hp-ux, eclipse-SDK-3.2.1-solaris-gtk as targetplattform) our config.ini
is not included in the build delivery.
The delivered config.ini contains following line "#Product Runtime
Configuration File" - maybe that might be a hint to our problem.

I don't know why the build on our build server does not deliver our
config.ini file?
There can't be any difference between all the build files used for the
build at our local machines and on the build server cause all build
files are fetched from the same cvs repository before the build starts.
The only difference are the target plattforms:
We are using eclipse-SDK-3.2.1-solaris-gtk on the build server and
eclipse-platform-SDK-3.2.1-win32.zip plus
eclipse-RCP-3.2.1-delta-pack.zip on our local machines.

Is there a known bug in eclipse-SDK-3.2.1-solaris-gtk?
We are thinking about moving to 3.3M6 as IDE & targetplattform - will
that solve that problem?

Who can help?

Kind regards,
Robert Reinhardt

Report message to a moderator

Re: Headless Build - customized config.ini is not delivered by automated headless build! [message #465630 is a reply to message #465496]

Tue, 03 April 2007 15:47

Andrew Niefer

Messages: 990
Registered: July 2009

Senior Member

Robert,
The "#Product Runtime Configuration File" is what pde.build puts at the top of
the config.ini file it generates.
The only way I see for this is that pde.build is not finding the custom
config.ini file. The only thing I can think of is to check the path that you
are giving for the config.ini file. This is expected to be of the form
"/<plugin-id | feature-id>/path/to/config.ini".
Note that the first segment is the plug-in or feature-id, which may be different
from the actual name of the project.

-Andrew
Robert Reinhardt wrote:
> Hi,
>
> Some weeks ago we have successfully introduced a headless automated
> build for our rcp application.
> The build is working on our locale dev-environments (using eclipse 3.2.1
> as ide & targetplattform on Win2K) and on our build server(Sun Solaris
> on a HPUx).
>
> Now he have introduced a shared configuration site that is configured
> via our customized config.ini file.
> In the launch config of the product at the Configuration/Configuration
> File section the option "Use an existing confing.ini as default template"
> The config.ini is located in our main feature and is located at a
> root/configuration folder that copies all files to a
> runtime/configuration folder during local build.
> The config.ini is stored in the cvs. The product that is refered by the
> build.properties refers to our customized config.ini.
>
> Our problem:
> At starting the headless build on our local machines everything works
> fine and the customized confing.ini is included in the builded client,
> but atstarting the headless build on our build server(sun solaris on
> hp-ux, eclipse-SDK-3.2.1-solaris-gtk as targetplattform) our config.ini
> is not included in the build delivery.
> The delivered config.ini contains following line "#Product Runtime
> Configuration File" - maybe that might be a hint to our problem.
>
> I don't know why the build on our build server does not deliver our
> config.ini file?
> There can't be any difference between all the build files used for the
> build at our local machines and on the build server cause all build
> files are fetched from the same cvs repository before the build starts.
> The only difference are the target plattforms:
> We are using eclipse-SDK-3.2.1-solaris-gtk on the build server and
> eclipse-platform-SDK-3.2.1-win32.zip plus
> eclipse-RCP-3.2.1-delta-pack.zip on our local machines.
>
> Is there a known bug in eclipse-SDK-3.2.1-solaris-gtk?
> We are thinking about moving to 3.3M6 as IDE & targetplattform - will
> that solve that problem?
>
> Who can help?
>
> Kind regards,
> Robert Reinhardt

Report message to a moderator

Previous Topic:	Eclipse Help and Java Web Start
Next Topic:	macosx rcp app

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 00:24:41 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter