|Target Platforms [message #640162]
||Fri, 19 November 2010 07:02
| Paul Warren
Registered: July 2009
I've done a bit of googling and not been able to find an answer so I thought
I'd try tis forum.
My understanding of a "target platform" is that it defines your applications
runtime environment. Is this understanding right?
I ask because the target platform almost always has to contain third party
libraries used during the testing phase of the project (or just for TDD).
We are building an RCP app. I want to make adding a dependency an explicit
decision driven by application requirements. We have a target definition
that grabs eclipse rcp sdk from the helios repo. My developers set this as
their target platform and bang - they can no longer pull in unnecessary
dependencies, just because they are there and too readily available when
building again in the default eclipse platform ide.
This is all fine, works very nicely.
Now I add a test bundle to my worksapce with some junits tests in order to
test a production bundle. My test bundle requires the org.junit bundle.
And now I get compilation errors because my target platform doesnt include
the org.junit bundle.
I can add it but I am loathe to do so because I think the target platform is
the essense of my products runtime environment, not its design time
environment. I dont want cross polination. I also dont want my release
build, that is based on our target definition, to have to require junit
Am I wrong in my understanding? Is there any other way to achieve this? Or
must I maintain two target definitions; a development definition for us
developers and a production definition for my release build?
Thanks in advance
|Re: Target Platforms [message #640967 is a reply to message #640318]
||Tue, 23 November 2010 12:26
| Curtis Windatt
Registered: July 2009
The launch configuration is based around the target platform. The general assumption is that whatever bundles you need to build (target platform) are also needed to launch (launch configuration). You can customize your launch configs to only launch certain plug-ins.|
You can also look at product configurations, which allow you to specify a set of dependencies that are a subset of your target. You can create launch configurations based on product configurations. In you case your target would have your runtime bundles + junit bundles, you product would only include the runtime bundles and when you launched the junit bundles would be left out.
There is a gap between launch configs, target definitions and product configurations that we would like to close. However, there are a lot of possible use cases and we need to support them all.
Powered by FUDForum
. Page generated in 0.01772 seconds