| Build RCP product/plugin with command line [message #482943] |
Fri, 28 August 2009 15:35  |
|
I'm using Eclipse 3.5 and I wanted to know if there is a solution to
automate build for product or plugin.
We can generate an Ant build.xml file which contains a usefull
'build.update.jar' target but it seems to be obsolete regarding the new
feature of a plugin exportation (source bundle for example).
So, generating a source bundle when exporting a plugin is not trivial
using the Ant configuration.
1) Is there any solution to get the same possibilities/options when
exporting through Ant as we have using the plugin exporter ?
2) Is there a way to create the same type of Ant file to create the final
RCP product ? (.exe, ...)
Thanks in advance,
Cédric
|
|
|
|
| Re: Build RCP product/plugin with command line [message #483003 is a reply to message #482943] |
Sat, 29 August 2009 05:18  |
|
This might also help:
http://www.vogella.de/articles/EclipsePDEBuild/article.html
Best regards, Lars
http://www.vogella.de/ - Eclipse plugin and Eclipse RCP Tutorials
http://www.twitter.com/vogella - vogella on Twitter
Opfermann Cédric wrote:
> I'm using Eclipse 3.5 and I wanted to know if there is a solution to
> automate build for product or plugin.
> We can generate an Ant build.xml file which contains a usefull
> 'build.update.jar' target but it seems to be obsolete regarding the new
> feature of a plugin exportation (source bundle for example).
> So, generating a source bundle when exporting a plugin is not trivial
> using the Ant configuration.
>
> 1) Is there any solution to get the same possibilities/options when
> exporting through Ant as we have using the plugin exporter ?
>
> 2) Is there a way to create the same type of Ant file to create the
> final RCP product ? (.exe, ...)
>
>
> Thanks in advance,
>
> Cédric
>
--
|
|
|
|
|
| Re: Build RCP product/plugin with command line [message #483178 is a reply to message #483059] |
Mon, 31 August 2009 13:43 |
|
| Christian wrote on Sun, 30 August 2009 10:31 |
Are these really up to date?
It seems these are from before p2 era. Creating update sites instead of
metadata repositories.
|
You're right, they are older but the cover the basics. It starts to diverge in 2 places (in 3.5):
1) you can consume p2 repos as part of your build, and create p2 map files (orbit has examples of p2 map files) example properties:
# a list of archived p2 repos to compile against
repoBaseLocation=${untransformed.dir}
transformedRepoLocation=${untransformed.dir}-trans
2) you add properties to cause p2 repos to be generated. For example:
# go p2
p2.repo=${buildDirectory}/${buildLabel}/repository
#generate.p2.metadata=true
p2.metadata.repo=file:${p2.repo}
p2.artifact.repo=file:${p2.repo}
p2.flavor=tooling
#p2.publish.artifacts=true
p2.root.name=${topLevelElementId}
p2.root.version=0.9.0.v${buildId}
p2.repo.name=e4 build ${buildId}
# This won't quite do what you want
#p2.category.site=file:${buildDirectory}/features/${topLevel ElementId}/site.xml
You can then assemble products using p2 director calls. But you're right, some of the latest support only came on line with the 3.5 builder and so while there are blogs and some help documentation, complex examples are sparse (although e4 is a p2 consuming PDE build based product).
PW
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
|
|
|
|
| Re: Build RCP product/plugin with command line [message #483275 is a reply to message #483270] |
Mon, 31 August 2009 20:31 |
|
Hi Christian,
> If I remember correctly my build produced products/zipfiles without
> executables in them.
If you follow exactly my tutorial this should not happen. If you are
able to reproduce this please let me know, I'll try to fix it.
> Also what I am still missing is an automated build for a set of
> features and a category.xml file.
True that is not covered by my tutorial.
Best regards, Lars
--
http://www.vogella.de/ - Eclipse plugin and Eclipse RCP Tutorials
http://www.twitter.com/vogella - vogella on Twitter
Christian wrote:
> Lars Vogel schrieb:
>> Hi Christian,
>>
>> which problem did you experience with my tutorial?
>>
>> Best regards, Lars
>>
>
> If I remember correctly my build produced products/zipfiles without
> executables in them.
>
>
> Also it did not cover everything I needed. And when the time I tried it
> I even had more misconceptions on p2 then I have right now. Also the
> lots of tutorials may have blurred a bit together... so probably I did
> some stuff wrong.. though I think it worked once or so and only after a
> few tries it stopped working(producing zip files without executables)..
> and I never found out what I did wrong.
>
> Also what I am still missing is an automated build for a set of features
> and a category.xml file.
>
|
|
|
| Re: Build RCP product/plugin with command line [message #484823 is a reply to message #483003] |
Wed, 09 September 2009 12:54 |
|
Thanks for the link, it was very helpful.
I notice that we have to launch the Ant script with the same JRE as the
workspace, but I think that this will be an issue for us because the final
goal it to launch the Ant script from a Mavem script.
In this case, there won't be any variable (like eclipse_home) defined in
the execution context.
Do you know if it's possible to launch the script from maven and which
variable we have to define ?
Thanks,
Cédric
|
|
|
Powered by
FUDForum. Page generated in 0.03116 seconds
] 
Search
Help
Register
Login
Home
