Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Rich Client Platform (RCP) » branding win32/linux rcp using ant
branding win32/linux rcp using ant [message #652250] Thu, 03 February 2011 10:27 Go to next message
Carmelo  is currently offline Carmelo Friend
Messages: 224
Registered: July 2009
Senior Member
Hi all
does anyone can point me in the right direction? I would love not to use the
"Eclipse product export wizard" but use an ant script ...

I have found something from vogella forum that helps me in doing the
operation but clearly doesn't do anything about the icons branding ...

any idea or forum where I could find something?


thanks
carmelo
Re: branding win32/linux rcp using ant [message #652277 is a reply to message #652250] Thu, 03 February 2011 12:49 Go to previous messageGo to next message
Paul Webster is currently offline Paul WebsterFriend
Messages: 6859
Registered: July 2009
Location: Ottawa
Senior Member

You want a product based PDE build.

See entries in Andrew Niefer's blog, like
http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.html

PW



--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Platform_Expression_Framework
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse .platform.doc.isv/guide/workbench.htm


Re: branding win32/linux rcp using ant [message #652346 is a reply to message #652277] Thu, 03 February 2011 16:00 Go to previous messageGo to next message
Carmelo  is currently offline Carmelo Friend
Messages: 224
Registered: July 2009
Senior Member
Hi Paul
I have read the article and tried on eclipse helios sr1.

I did download the example and followed the steps ... I have tried with the
simplecofigurator and not ... but still not able to build my example test
.....

I have tried with a simple config line ... and either multiple configs

configs = win32, win32, x86 & \
macosx, carbon, x86

(someone was saying about config problem when single line was used ... but
still don't know). ... why it stop in searching .aix.ppc_0.0.0 ???

thanks carmelo






Buildfile:
E:\devel\BuildTest\workspace\org.eclipse.pde.build\scripts\p roductBuild\productBuild.xml

main:

preBuild:

preSetup:
[copy] Copying 1 file to E:\devel\BuildTest\workspace\Builder
[delete] Deleting: E:\devel\BuildTest\workspace\Builder\product.version

checkLocalMaps:

getMapFiles:

postSetup:

checkLocalBase:

getBaseComponents:

processRepos:

generateFeature:

fetch:

generateFeature:
[eclipse.generateFeature] Some inter-plug-in dependencies have not been
satisfied.
[eclipse.generateFeature] Bundle org.eclipse.wst.xsl.exslt.ui.tests:
[eclipse.generateFeature] Missing required plug-in
org.eclipse.wst.xsl.ui.tests_[1.0.0,2.0.0).
[eclipse.generateFeature] Bundle org.eclipse.wst.xsl.tests:
[eclipse.generateFeature] Missing required plug-in
org.eclipse.wst.xsl.ui.tests_1.0.0.
[eclipse.generateFeature] Missing required plug-in
org.eclipse.wst.xml.xpath2.processor.tests_1.0.0.
[eclipse.generateFeature] Missing required plug-in
org.eclipse.wst.xsl.exslt.ui.tests_1.0.0.
[eclipse.generateFeature] Missing required plug-in
org.eclipse.wst.xml.xpath.ui.tests_1.0.0.

BUILD FAILED
E:\devel\BuildTest\workspace\org.eclipse.pde.build\scripts\p roductBuild\productBuild.xml:39:
The following error occurred while executing this line:
E:\devel\BuildTest\workspace\org.eclipse.pde.build\scripts\p roductBuild\productBuild.xml:69:
Unable to find plug-in: org.eclipse.core.filesystem.aix.ppc_0.0.0. Please
check the error log for more details.

Total time: 4 seconds
An error has occurred. See the log file
E:\devel\BuildTest\runtime-New_configuration\.metadata\.log.




"Paul Webster" <pwebster@ca.ibm.com> ha scritto nel messaggio
news:iie7ov$jsv$2@news.eclipse.org...
> You want a product based PDE build.
>
> See entries in Andrew Niefer's blog, like
> http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.html
>
> PW
>
>
>
> --
> Paul Webster
> http://wiki.eclipse.org/Platform_Command_Framework
> http://wiki.eclipse.org/Command_Core_Expressions
> http://wiki.eclipse.org/Platform_Expression_Framework
> http://wiki.eclipse.org/Menu_Contributions
> http://wiki.eclipse.org/Menus_Extension_Mapping
> http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse .platform.doc.isv/guide/workbench.htm
>
Re: branding win32/linux rcp using ant [message #652436 is a reply to message #652250] Thu, 03 February 2011 22:01 Go to previous messageGo to next message
Catalin Gerea is currently offline Catalin GereaFriend
Messages: 89
Registered: July 2009
Location: Bucharest, Romania
Member

Hello

It is possible to brand a win32/linux rcp application using ant. It is better to do this at the beginning because it is easier to debug build problems. When you have an rcp application with multiple plugins it is sometimes very hard to debug. More over sometimes the PDE error messages are not very clear.

Do you have an product configuration based on plugins or features? I assume that it is a plugins based one.

In your actual situation:
1. Just try to use only a single config like 'win32, win32, x86' to see if you still have the problem.
2. Then you should check your product/feature definition (to see if you do not have the .aix. referenced there). Put in your product definition only the necessary plug-ins.
3. As debug procedure: remove all plugins from your product definition and then add the plugins one by one to the product definition (from your launch configuration). Every time you add a plugin you create the build and see if still works.
4. Or you can create a product configuration from an working launch configuration and use this product configuration in the build.

Remember that for multiple configurations you need the delta pack.

In the future you can try the step-by-step approach:
1. Start from a single plugin.
2. Create the ant build using a single config like 'win32, win32, x86' and see if it works.
3. If you are using the headless PDE build with ant then you can integrate the build with a continuous integration tool like Hudson/CruiseControl. This way when you make a change to your application you can quickly see what made the build to fail.


Time is what you make of it.
Re: branding win32/linux rcp using ant [message #652479 is a reply to message #652436] Fri, 04 February 2011 08:59 Go to previous messageGo to next message
Carmelo  is currently offline Carmelo Friend
Messages: 224
Registered: July 2009
Senior Member
Hi and thank for your help ...
the example I was testing was the one from the article ...

this is based on plugin but my final rcp it is based on feature ... so I
will need to adjust it for feature ...

I will try to see if there is any wrong dependency (and if you have any
tutorial / link ... whatever) that can tell me what to change to have a
build rcp headless for rcp (based on feature) able to build and replace the
eclipse.exe that would be nice.

thanks in advance
carmelo


"Catalin Gerea" <gereac@gmail.com> ha scritto nel messaggio
news:iif88h$m21$1@news.eclipse.org...
> Hello
>
> It is possible to brand a win32/linux rcp application using ant. It is
> better to do this at the beginning because it is easier to debug build
> problems. When you have an rcp application with multiple plugins it is
> sometimes very hard to debug. More over sometimes the PDE error messages
> are not very clear.
>
> Do you have an product configuration based on plugins or features? I
> assume that it is a plugins based one.
>
> In your actual situation:
> 1. Just try to use only a single config like 'win32, win32, x86' to see if
> you still have the problem.
> 2. Then you should check your product/feature definition (to see if you do
> not have the .aix. referenced there). Put in your product definition only
> the necessary plug-ins.
> 3. As debug procedure: remove all plugins from your product definition and
> then add the plugins one by one to the product definition (from your
> launch configuration). Every time you add a plugin you create the build
> and see if still works.
> 4. Or you can create a product configuration from an working launch
> configuration and use this product configuration in the build.
>
> Remember that for multiple configurations you need the delta pack.
>
> In the future you can try the step-by-step approach:
> 1. Start from a single plugin.
> 2. Create the ant build using a single config like 'win32, win32, x86' and
> see if it works.
> 3. If you are using the headless PDE build with ant then you can integrate
> the build with a continuous integration tool like Hudson/CruiseControl.
> This way when you make a change to your application you can quickly see
> what made the build to fail.
> --
> Time is what you make of it.
Re: branding win32/linux rcp using ant [message #652532 is a reply to message #652250] Fri, 04 February 2011 12:43 Go to previous messageGo to next message
Catalin Gerea is currently offline Catalin GereaFriend
Messages: 89
Registered: July 2009
Location: Bucharest, Romania
Member

Hello

At my work we are using a plugin based definition without branding; at home as exercise I am using a feature based definition with branding. Both of them are headless PDE builds using ANT.

It doesn't matter if it is plugin or feature based. For you the debug steps are:
- use only one feature (if you are using multiple features in your product definition). If it works then add an additional one and so forth.
- in the feature definition add the plugins one by one until it works.

I know this will take a lot of time (at work it took me a day and a half to make it work). As I said: in the product definition based on plugins or in the feature definition there is no 'Add required plugins' as in the launch configuration.

Therefore problems like yours will appear.

Links for the headless PDE build (no particular order):
http://richardadams606blog.blogspot.com/2010/04/eclipse-rcp- headless-build-experiences.html
http://www.toedter.com/blog/?p=26
http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.html
http://www.modumind.com/2007/06/06/getting-started-with-pde- build/?bcsi-ac-ED4481DDE3DE1057=1BFC705000000503DTSKyi6iQmJh GdAZGWTaws00/iX1BgAAAwUAANRbaAAIBwAAEwAAALdhCQA=
http://www.vogella.de/articles/EclipsePDEBuild/article.html
http://blog.ankursharma.org/2010/06/headless-build-for-begin ners-part-i.html

Also try first the headless build without the p2 part. Then you can add it to the build.


Time is what you make of it.
Re: branding win32/linux rcp using ant [message #652544 is a reply to message #652532] Fri, 04 February 2011 13:39 Go to previous messageGo to next message
Carmelo  is currently offline Carmelo Friend
Messages: 224
Registered: July 2009
Senior Member
I'm reading right now the following post ... but clearly not easy to follow
and every time I try to build the really basic example I get errors ... hope
by the end of the day I will be able to find one method that works fine from
beginning to end :-)

from what I have read the buckminster plugin looks like is going to be the
feature of building with helios ... let's see if I get something working or
I will get back to the other (hopefully simpler approach).

thanks for your help
ciao
carmelo


http://www.ralfebert.de/blog/eclipsercp/rcp_builds/




"Catalin Gerea" <gereac@gmail.com> ha scritto nel messaggio
news:iigruv$afi$1@news.eclipse.org...
> Hello
>
> At my work we are using a plugin based definition without branding; at
> home as exercise I am using a feature based definition with branding. Both
> of them are headless PDE builds using ANT.
>
> It doesn't matter if it is plugin or feature based. For you the debug
> steps are:
> - use only one feature (if you are using multiple features in your product
> definition). If it works then add an additional one and so forth.
> - in the feature definition add the plugins one by one until it works.
>
> I know this will take a lot of time (at work it took me a day and a half
> to make it work). As I said: in the product definition based on plugins
> or in the feature definition there is no 'Add required plugins' as in the
> launch configuration.
>
> Therefore problems like yours will appear.
>
> Links for the headless PDE build (no particular order):
> http://richardadams606blog.blogspot.com/2010/04/eclipse-rcp- headless-build-experiences.html
> http://www.toedter.com/blog/?p=26
> http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.html
> http://www.modumind.com/2007/06/06/getting-started-with-pde- build/?bcsi-ac-ED4481DDE3DE1057=1BFC705000000503DTSKyi6iQmJh GdAZGWTaws00/iX1BgAAAwUAANRbaAAIBwAAEwAAALdhCQA=
> http://www.vogella.de/articles/EclipsePDEBuild/article.html
> http://blog.ankursharma.org/2010/06/headless-build-for-begin ners-part-i.html
>
> Also try first the headless build without the p2 part. Then you can add it
> to the build.
> --
> Time is what you make of it.
Re: branding win32/linux rcp using ant [message #653323 is a reply to message #652544] Wed, 09 February 2011 11:38 Go to previous messageGo to next message
Carmelo  is currently offline Carmelo Friend
Messages: 224
Registered: July 2009
Senior Member
HI all,
after two more days of frustration ... I'm totally lost :(

I was trying to keep the headless build as simple as possible ... so I
decided to use the path of using the build templates file
( http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.html)

but ... with helios ... looks like the situation doesn't work really well
(even reading all the notes from different users ...)
I can get the folder generated but not exe is created

note:

org.eclipse.equinox.executable - this doesn't exist anymore

if I don't put this ... the generated folder have got only the p2 repository
....


the other way... simpler using the Buckminster works fine with feature ...
but I'm not sure this is the better COMMON approach ...

bring me some lights please
ciao
carmelo



"Kar" <carmeloscala@hotmail.com> ha scritto nel messaggio
news:iigvau$h4d$1@news.eclipse.org...
> I'm reading right now the following post ... but clearly not easy to
> follow and every time I try to build the really basic example I get errors
> ... hope by the end of the day I will be able to find one method that
> works fine from beginning to end :-)
>
> from what I have read the buckminster plugin looks like is going to be the
> feature of building with helios ... let's see if I get something working
> or I will get back to the other (hopefully simpler approach).
>
> thanks for your help
> ciao
> carmelo
>
>
> http://www.ralfebert.de/blog/eclipsercp/rcp_builds/
>
>
>
>
> "Catalin Gerea" <gereac@gmail.com> ha scritto nel messaggio
> news:iigruv$afi$1@news.eclipse.org...
>> Hello
>>
>> At my work we are using a plugin based definition without branding; at
>> home as exercise I am using a feature based definition with branding.
>> Both of them are headless PDE builds using ANT.
>>
>> It doesn't matter if it is plugin or feature based. For you the debug
>> steps are:
>> - use only one feature (if you are using multiple features in your
>> product definition). If it works then add an additional one and so forth.
>> - in the feature definition add the plugins one by one until it works.
>>
>> I know this will take a lot of time (at work it took me a day and a half
>> to make it work). As I said: in the product definition based on plugins
>> or in the feature definition there is no 'Add required plugins' as in the
>> launch configuration.
>>
>> Therefore problems like yours will appear.
>>
>> Links for the headless PDE build (no particular order):
>> http://richardadams606blog.blogspot.com/2010/04/eclipse-rcp- headless-build-experiences.html
>> http://www.toedter.com/blog/?p=26
>> http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.html
>> http://www.modumind.com/2007/06/06/getting-started-with-pde- build/?bcsi-ac-ED4481DDE3DE1057=1BFC705000000503DTSKyi6iQmJh GdAZGWTaws00/iX1BgAAAwUAANRbaAAIBwAAEwAAALdhCQA=
>> http://www.vogella.de/articles/EclipsePDEBuild/article.html
>> http://blog.ankursharma.org/2010/06/headless-build-for-begin ners-part-i.html
>>
>> Also try first the headless build without the p2 part. Then you can add
>> it to the build.
>> --
>> Time is what you make of it.
>
Re: branding win32/linux rcp using ant [message #653469 is a reply to message #653323] Wed, 09 February 2011 20:47 Go to previous message
Catalin Gerea is currently offline Catalin GereaFriend
Messages: 89
Registered: July 2009
Location: Bucharest, Romania
Member

Hello

1. No exe generated could come from some different points:
a) One is the missing delta pack; (most likely from my point if view)
b) in your product definition you did not checked the 'This product includes native launcher artifacts' checkbox.

2. "org.eclipse.equinox.executable" is in the delta pack (delta pack was pointed both by me and in the article by Andrew Niefer). See http://aniefer.blogspot.com/2009/06/using-deltapack-in-eclip se-35.html for delta pack information.

But if Buckminster is working for you and you do not have any kind of restriction in using it, then go ahead with.

I do not read anything about a 'common approach' when it comes to building RCP applications. Everybody uses the solution that works in his/her environment (Buckminster, Tycho, PDE headless build, PDE Export from IDE).

P.S. I did not used Buckminster so I cannot tell why it works in your case.


Time is what you make of it.
Previous Topic:How To set Dataformat for DateTime widget
Next Topic:PerspectiveBarManager: how to avoid Discouraged access?
Goto Forum:
  


Current Time: Sat Dec 20 03:46:10 GMT 2014

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

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