<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Ian,<br>
<br>
For our internal dependencies between jbosstools components, we
don't use the target-platform. Most of JBoss Tools developers have
their dependencies opened as project in the workspace.<br>
<br>
for you use-case, you could:<br>
* either import the bundle you depend on in your workspace. The
benefit is that you can see and change its code, which can be
helpful, or<br>
* create your own target platform and include into it the test
bundles<br>
<pre><div class="line" id="LC19"> <location includeAllPlatforms="false" includeMode="slicer" type="InstallableUnit" includeSource="true"></div><div class="line" id="LC22"> <repository location=<a class="moz-txt-link-rfc2396E" href="http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.1.kepler/">"http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.1.kepler/"</a>/>
</div><div class="line" id="LC25"> <unit id="org.jboss.tools.tests" version="0.0.0"/>
<!-- version 0.0.0 will select the best version, so if version changes on site, you won't need to update it there -->
</location>
</div>
</pre>
Hope this helps. Feel free to ask for more if necessary.<br>
You might also discuss with Max (Andersen) about whether your plugin
should already be shaped as a JBoss Tools component and part of a
future JBoss Tools release.<br>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a href="http://www.jboss.org/tools">JBoss,
by Red Hat</a><br>
<a href="http://mickaelistria.wordpress.com">My blog</a> - <a
href="http://twitter.com/mickaelistria">My Tweets</a></div>
</body>
</html>