| Eclipse target platform, workspace components and 3rd party bundles / JARS [message #536286] |
Thu, 27 May 2010 10:21  |
Eclipse User |
|
|
|
Here is a quick summary of what I did to setup a materialization of 3rd
party jars into an Eclipse target platform:
1. Create a Feature that lists all the required 3rd party bundles that you
are using as plug-ins that are "packaged into the feature".
2. Create an Update Site project, add the Feature from step 1 above to the
"Site Map".
3. Buckminster CSPEC - write a CSPEC that has the feature in step 1 as the
root node for the query.
4. Buckminster RMAP - Something like this:
<searchPath name="externals">
<provider readerType="eclipse.import"
componentTypes="osgi.bundle,eclipse.feature" mutable="false" source="false">
<uri format="file:/${site.path.3rdpartybundles}?importType=linked "
/>
</provider>
</searchPath>
5. Buckminster MSPEC - references CSPEC above, something like this:
<?xml version="1.0" encoding="UTF-8"?>
<mspec xmlns="http://www.eclipse.org/buckminster/MetaData-1.0"
name="Target Platform MSPEC" materializer="p2"
installLocation="${targetPlatformPath}"
url="tp.cquery">
<property key="target.arch" value="*"/>
<property key="target.os" value="*"/>
<property key="target.ws" value="*"/>
</mspec>
6. In Eclipse, right click on the MSPEC, Import... -> Buckminster ->
Materialize... then you can choose where you want the materialized bundles
to go.
I still have some open questions on the whole process:
Is there a way that I can combine the target platform and workspace setup
into one CQUERY or MSPEC? Or would this be bad practice?
|
|
|
|
Powered by
FUDForum. Page generated in 0.03911 seconds
Home