Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » Target Definition(How do I best manage my targets?)
Target Definition [message #989910] Sun, 09 December 2012 22:27 Go to next message
Eban Escott is currently offline Eban EscottFriend
Messages: 61
Registered: July 2009
Member
Hi,

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.

http://wiki.eclipse.org/PDE/Target_Definitions

Cheers
Eban
Re: Target Definition [message #997019 is a reply to message #989910] Thu, 03 January 2013 12:21 Go to previous messageGo to next message
maarten meijer is currently offline maarten meijerFriend
Messages: 145
Registered: July 2009
Senior Member
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.

Maarten


Op 09-12-12 23:27, Eban Escott schreef:
> Hi,
>
> 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.
>
> http://wiki.eclipse.org/PDE/Target_Definitions
>
> Cheers
> Eban
Re: Target Definition [message #1000610 is a reply to message #997019] Tue, 15 January 2013 05:14 Go to previous messageGo to next message
Eban Escott is currently offline Eban EscottFriend
Messages: 61
Registered: July 2009
Member
Hi Maarten,

Thanks for the response. I am not building an RCP application, I am building an OSGi-based web application that does not use RCP.

So, I have a target definition containing all bundles that are used by the deployed application. Then I can use a launch configuration to start the application.

I do not see how a product definition would help. Any ideas?

Cheers
Eban
Re: Target Definition [message #1000617 is a reply to message #1000610] Tue, 15 January 2013 05:20 Go to previous message
Ed Merks is currently offline Ed MerksFriend
Messages: 26215
Registered: July 2009
Senior Member
Eban,

In the launcher you can specify which bundles you want on the classpath
at runtime. If you need things for compilation, you definitely need to
leave them in your target platform (on the Plug-ins tab).


On 15/01/2013 6:14 AM, Eban Escott wrote:
> Hi Maarten,
>
> Thanks for the response. I am not building an RCP application, I am
> building an OSGi-based web application that does not use RCP.
>
> So, I have a target definition containing all bundles that are used by
> the deployed application. Then I can use a launch configuration to
> start the application.
>
> I do not see how a product definition would help. Any ideas?
>
> Cheers
> Eban
Previous Topic:Out of memory after Clean-Autobuild multiple times with custom builder by org.eclipse.core.internal.
Next Topic:No more handles [gtk_init_check() failed]
Goto Forum:
  


Current Time: Mon Nov 24 03:11:53 GMT 2014

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

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