| [tycho-user] Using Tycho to Build Custom Target Platform |
Hello everybody, can you guys please have a look at the attached sample projects? I'm trying to get this to work for days now and I don't know where to look for further hints anymore... I'm trying to build my own custom target platform for Eclipse RCP development with Tycho. The platform should contain an individually selected subset of Eclipse plugins aggregated within a custom feature. Additional features should then contain several plugins wrapping thirdparty Java libraries as bundles (in this example com.thoughtworks.xstream). The first part already works, but with the second part I'm running into problems: While building the plugin com.thoughtworks.xstream wrapping the XStream library works, Tycho runs into problems resolving the dependency to that plugin when building the com.thoughtworks.xstream.feature. I do understand why (Tycho tries to resolve the included plugin com.thoughtworks.xstream via the configured target platform update site http://download.eclipse.org/releases/indigo/), but I don't know how to change this. I would need to make Tycho resolve the dependency against the local Maven repository where the com.thoughtworks.xstream artifact has been placed by building it one step ahead using standard Maven. Do you have any hint how to get this to work? Or are there any other ways to achieve my goal? I appreciate any hint, comment, suggestion, ... To build the attached sample projects proceed as follows: 1) Extract the projects to a new and empty workspace (Eclipse Indigo). 2) Run Maven install on the com.example.targetplatform.parent project. 3) Run Maven install on the com.example.targetplatform.rcp.feature project. 4) Run Maven install on the com.thoughtworks.xstream project. 5) Run Maven install on the com.thoughtworks.xstream.feature project - this will fail. 6) Run Maven package on the com.example.targetplatform.parent project. This works since I did not include the failing com.thoughtworks.xstream.feature in the category.xml file so far. There it would be placed to be included in the resulting repository later. Thank you very much Timo Rohrberg
Attachment:
custom_targetplatform_build.zip
Description: Zip archive