Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Rich Client Platform (RCP) » Building ready-to-use RCP product with org.eclipse.releng.basebuilder
Building ready-to-use RCP product with org.eclipse.releng.basebuilder [message #446353] Sun, 19 March 2006 17:09 Go to next message
Eclipse UserFriend
Originally posted by: mehow.remove.neurosoft.net

Hi,

I'm following an article at
http://www.eclipse.org/articles/Article-PDE-Automation/autom ation.html
as well as a document at
http://dev.eclipse.org/viewcvs/index.cgi/*checkout*/org.ecli pse.releng.basebuilder/readme.html?rev=HEAD&content-type =text/html
trying to setup an automated headless build for my RCP application.
Most of the steps are already working, but I have problems configuring
packaging step.

Although the documents don't describe product branding, it seems to be
supported with a "product" property, which I had properly set in my
build.properties. Unfortunately, during packaging I get
java.io.EOFException from eclipse.brand task located in generated
assemble.<my.feature>.win32.win32.x86.xml script. This seems to be
caused by the fact that eclipse.exe is not copied to the target
directory (set in root attribute of the task) before the task is executed.

I guess I could just copy it there in one of the customTargets.xml
targets, but I believe there's already some infrastructure for that in
the org.eclipse.releng.basebuilder itself.
In particular packaging.properties files that I found in
org.eclipse.releng.eclipsebuilder project seem to leverage that
infrastructure. Unfortunately I couldn't find any documentation about
how to setup it in existing customTargets.xml.

Can anyone please tell me how to do this?

Thanks in advance,

Michal
Re: Building ready-to-use RCP product with org.eclipse.releng.basebuilder [message #454125 is a reply to message #446353] Mon, 21 August 2006 08:57 Go to previous messageGo to next message
Stefan Lötscher is currently offline Stefan LötscherFriend
Messages: 9
Registered: July 2009
Junior Member
Hi Michal

Currently I'm setting up an automatic build of our RCP application and
I've experienced the same problem you described in the different news groups
back in March 06. Unfortunately nobody replied to them as far as I know. Did
you solve the problem? 

Can you help me? Where do I have to put the DeltaPacks? The build platform
is OS X and the target platforms are OS X and Win32 


Thanks in advance

Stephan

Am 19.3.2006 19:09 Uhr schrieb "Michał Tkacz" unter
<mehow.remove@neurosoft.net> in dvk38p$on4$1@utils.eclipse.org:

> Hi,
>
> I'm following an article at
> http://www.eclipse.org/articles/Article-PDE-Automation/autom ation.html
> as well as a document at
> http://dev.eclipse.org/viewcvs/index.cgi/*checkout*/org.ecli pse.releng.basebui
> lder/readme.html?rev=HEAD&content-type=text/html
> trying to setup an automated headless build for my RCP application.
> Most of the steps are already working, but I have problems configuring
> packaging step.
>
> Although the documents don't describe product branding, it seems to be
> supported with a "product" property, which I had properly set in my
> build.properties. Unfortunately, during packaging I get
> java.io.EOFException from eclipse.brand task located in generated
> assemble.<my.feature>.win32.win32.x86.xml script. This seems to be
> caused by the fact that eclipse.exe is not copied to the target
> directory (set in root attribute of the task) before the task is executed.
>
> I guess I could just copy it there in one of the customTargets.xml
> targets, but I believe there's already some infrastructure for that in
> the org.eclipse.releng.basebuilder itself.
> In particular packaging.properties files that I found in
> org.eclipse.releng.eclipsebuilder project seem to leverage that
> infrastructure. Unfortunately I couldn't find any documentation about
> how to setup it in existing customTargets.xml.
>
> Can anyone please tell me how to do this?
>
> Thanks in advance,
>
> Michal
Re: Building ready-to-use RCP product withorg.eclipse.releng.basebuilder [message #454867 is a reply to message #454125] Fri, 08 September 2006 19:32 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: VaughnWi.attachmate.com

Looks like BrandingIron is creating an empty eclipse.exe and then later,
when it attempts to read the existing icons in the file, throws the
EOFException. I might be able to get around this by copying the executable
before the build...

Has anybody else seen this issue. Looks like a bug, but I might be doing
something wrong in my PDE Build setup...




Thanks!



Vaughn





"Stefan L
Re: Building ready-to-use RCP product with org.eclipse.releng.basebuilder [message #454948 is a reply to message #454125] Mon, 11 September 2006 15:39 Go to previous messageGo to next message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
You should put the delta pack in the ${baseLocation} with the rest of
your target eclipse.

-Andrew

Stefan Lötscher wrote:
> Hi Michal
>
> Currently I'm setting up an automatic build of our RCP application and
> I've experienced the same problem you described in the different news groups
> back in March 06. Unfortunately nobody replied to them as far as I know. Did
> you solve the problem?
>
> Can you help me? Where do I have to put the DeltaPacks? The build platform
> is OS X and the target platforms are OS X and Win32
>
>
> Thanks in advance
>
> Stephan
>
Re: Building ready-to-use RCP product withorg.eclipse.releng.basebuilder [message #454949 is a reply to message #454867] Mon, 11 September 2006 15:47 Go to previous messageGo to next message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
This exception does come from when the eclipse.exe does not exist when
the branding is called.

Setting the product property by itself is not sufficient to get the
eclipse.exe. You need to have the org.eclipse.platform.launchers
feature included in your main feature. This platform.launchers feature
contains the eclipse.exe as a root file. (Or if you don't include the
launcher feature, you need a similar feature which has the eclipse.exe
as a rootfile.)

-Andrew

Vaughn Wine wrote:
> Looks like BrandingIron is creating an empty eclipse.exe and then later,
> when it attempts to read the existing icons in the file, throws the
> EOFException. I might be able to get around this by copying the executable
> before the build...
>
> Has anybody else seen this issue. Looks like a bug, but I might be doing
> something wrong in my PDE Build setup...
>
>>>
>>> Although the documents don't describe product branding, it seems to be
>>> supported with a "product" property, which I had properly set in my
>>> build.properties. Unfortunately, during packaging I get
>>> java.io.EOFException from eclipse.brand task located in generated
>>> assemble.<my.feature>.win32.win32.x86.xml script. This seems to be
>>> caused by the fact that eclipse.exe is not copied to the target
>>> directory (set in root attribute of the task) before the task is
>>> executed.
>>>
>>> Can anyone please tell me how to do this?
>>>
>>> Thanks in advance,
>>>
>>> Michal
>
>
Re: Building ready-to-use RCP product with org.eclipse.releng.basebuilder [message #455078 is a reply to message #454948] Thu, 14 September 2006 19:20 Go to previous message
Eclipse UserFriend
Originally posted by: VaughnWi.attachmate.com

After installing the delta pack, I simply added the
org.eclipse.platform.launchers to my top-level "dummy" product feature, and
everything began to work...

Thanks Andrew! Thanks also to Stephan L
Previous Topic:version numbers and subversion
Next Topic:How to get order order of editor tabs
Goto Forum:
  


Current Time: Fri Apr 26 13:15:17 GMT 2024

Powered by FUDForum. Page generated in 0.03000 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top