| Re: [tycho-user] Hiding Source Features in Custom Target Platform |
Hello, I adapted the sample projects a little and am now using the tycho-source-plugin to build separate source bundles. I think that's definitely a better approach than I did it in the version this morning. Unfortunately, now Tycho is unable to find the com.example.logging-1.6.1-sources.jar file to resolve the com.example.logging.source plugin in the com.example.logging.source.feature. I just don't know how to correctly point Tycho to the com.example.logging-1.6.1-sources.jar which is available in my local Maven repository after building the com.example.logging plugin successfully with Tycho. Do you have any ideas how to resolve this issue? Thank you for any hints, comments, etc. Regards Timo 2011/10/13 Timo Rohrberg <rti.init@xxxxxxxxxxxxxx>: > Hello everybody, > > with your help, I finally got my custom target platform build to work > (see my recent posting on this mailinglist). But there's still one > issue I would like to solve: Is there a way to hide source features > from the user when building the final update site project with tycho? > When configuring a target platform in Eclipse using default p2 > locations, such as http://downloads.eclipse.org/releases/indigo, only > one feature is shown to the user for each element (e.g. feature for > org.eclipse.rcp, but not for org.eclipse.rcp.source). If the user > selects the option "Include source if available", the resolution > process downloads both features and their listed plugins. > > In contrary, two features are shown to the user in my case (see > attached sample projects), and the user explicitely needs to select > both of them to gain source code access. The option "Include source if > available" seems to be ignored in my case. > > Proceed as follows to reproduce the issue with the attached sample projects: > > 1) Extract attached zip file into a new and clean Eclipse Indigo workspace. > 2) Subsequently run Maven Install on the projects; Maven Package > suffices on com.example.repository. > 3) Now grab the result from com.example.repository/target/repository > and place it to a webspace of your choice. > 4) Create a new Eclipse Indigo Workspace. > 5) Configure Target Platform to include local Eclipse Indigo > installation directory, plus the repository generated above. Do not > select the source feature in the first step, and do not activate the > option "Include source if available". > 6) Create a new RCP project (e.g. Hello RCP demo) and import the > package org.slf4f in its MANIFEST.MF. > 7) Inspect that you have access to the com.example.logging jar, but > not its sources. > 8) To gain access to the sources, the only way is to select the source > feature in the target platform setup. Activating the option "Include > source if available" does not help. > > Do you guys have any hints? I appreciate any help you can give me. > > Regards > Timo >
Attachment:
custom_targetplatform_build_v4.zip
Description: Zip archive