|Re: Target Definition [message #997019 is a reply to message #989910]
||Thu, 03 January 2013 12:21
| maarten meijer
Registered: July 2009
As I think you're confusing target and product definition:|
- The target definition contains everything you need at development
time: platform, junit, other plugins, ....
- The product definition contains everything you want to export into
your RCP application, specied as features containing features and plugins.
When you need stuff at compile time, you're not "polluting the target
definition", when you export everything later on you are.
As reference, when doing RCP development you should include the source
bundles, so you get the definitions of all the extension point for your
plugin.xml. But you don't need to export these source bundles for the
application to run.
Op 09-12-12 23:27, Eban Escott schreef:
> If I have bundles that are only required at compile-time and not at
> run-time, what is the best way to manage my target? i.e. I am using some
> modelling tools that are not required when I start my application and I
> do not want to pollute my target definition with compile-time only
> bundles as it will get very large quickly.
Powered by FUDForum
. Page generated in 0.04724 seconds