Community
Participate
Working Groups
Build Identifier: Build id: 20100917-0705 A feature cannot be build from a target definition if it contains: Eclipse Platform SDK 3.6.1.M20100909-0800 Reproducible: Always Steps to Reproduce: 0. Make sure you have a clean workspace. 1.Create a new .target file. 2.Add the p2 site: http://download.eclipse.org/eclipse/updates/3.6 3. Select the : Eclipse Platform SDK 3.6.1.M20100909-0800 feature. Make sure to Deselect "Include required software" and Select "Include all environments". Press finish and wait for the target to be loaded. 4. Press "Set as Target Platform". 5. Create a new eclipse feature and when asked for plugins/fragments to add select all (corresponding the the currently selected target). 6. Export the feature to a local archive on disk. As a result you should get the error: Processing inclusion from feature target.feature: Bundle org.eclipse.core.filesystem.aix.ppc_1.1.0.v20100505-1235 failed to resolve.: Alternatively. After setting the target platform create a new run configuration (eclipse application) and select all plugins from the target. Press validate. This gives a lot of "Platform Filter did not match" errors.
cc'd Andrew in case he can give a better answer. This strikes me as working as designed. You added things to your target platform that don't apply to the platform you are running on. Feature export only works for your running platform unless you use the delta pack support. Launching only works for the running platform because it has to launch.
(In reply to comment #1) > cc'd Andrew in case he can give a better answer. > > This strikes me as working as designed. You added things to your target > platform that don't apply to the platform you are running on. Feature export > only works for your running platform unless you use the delta pack support. > Launching only works for the running platform because it has to launch. Maybe not the most convincing argument but this tutorial has worked fine: http://nirmalsasidharan.wordpress.com/2010/10/09/provisioning-your-target-platform-as-local-p2-site/ In the above tutorial section "3. Creating a new target platform feature" an update site is build from a feature as described in my orginal post (from a target platform with "Include all environments" - basically that corresponds to downloading the delta pack). Next an update site is build from this feature, but this is currently not possible since the feature cannot be build and hence the update site cannot be build (gives the same error when building an update site from the feature described in the original post). But maybe this approach is simply not supported anymore?
(In reply to comment #2) > (In reply to comment #1) > > cc'd Andrew in case he can give a better answer. > > > > This strikes me as working as designed. You added things to your target > > platform that don't apply to the platform you are running on. Feature export > > only works for your running platform unless you use the delta pack support. > > Launching only works for the running platform because it has to launch. > > Maybe not the most convincing argument but this tutorial has worked fine: > > http://nirmalsasidharan.wordpress.com/2010/10/09/provisioning-your-target-platform-as-local-p2-site/ > > In the above tutorial section "3. Creating a new target platform feature" an > update site is build from a feature as described in my orginal post (from a > target platform with "Include all environments" - basically that corresponds to > downloading the delta pack). > > Next an update site is build from this feature, but this is currently not > possible since the feature cannot be build and hence the update site cannot be > build (gives the same error when building an update site from the feature > described in the original post). > > But maybe this approach is simply not supported anymore? Sorry for some reason it skipped my attention that the tutorial says: 4. Creating a p2 site for target platform You could do this either using PDE or using Buckminster. If you want your target platform to support multiple development platforms (OSX, Linux, Windows etc.) use Buckminster (unfortunately, PDE had some export issues doing this) So its recognized that pde does not support this type of multiple os target/updatesite export and buckmeister must be used instead.
Note that in 3.7 there is a new target export mechanism that should allow you to export your target definitions and get exactly what is being used in the workspace. This is not exactly what you are talking about here but it may be of some help.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This bug has been marked as stalebug a while ago without any further interaction. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.
This bug was marked as stalebug a while ago. Marking as worksforme. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
