Community
Participate
Working Groups
Build Identifier: 3.7 We have a project (svn) that contains our target platform. I'd like to define the PDE Target platform using variable to make the definition relative to the project. Adding a folder using ${resource_loc} works fine but adding a feature using this variable fails. see this screen shot : https://skitch.com/sgandon/gjp1b/edit-target-definition Reproducible: Always
When creating the feature, the editor reads the feature list correctly and displays all of them, then I select them all and click finish. Then in the Target Content Dialog you have plenty of errors stating : unable to locate feature XXXX
The feature location uses directory locations with some code to filter out the unwanted features. We are just missing a variable resolution somewhere. A stack trace would be helpful, but the editor won't produce one in this case.
Fixed in master. However, you can likely work around the issue by pointing your locations one directory higher (the parent folder of the features folder). The problem wasn't that we were missing a variable resolve, instead the problem is that the PluginPathFinder always assumes there will be a features folder. I changed the code to use the provided directory if no features folder or linked folders are found. While working on this issue I uncovered a larger regression with how the UI handles features since the target API change. We were in some places still passing around IFeatureModels instead of the new TargetFeature API. The feature target location code still uses IFeatureModel and we use it internally inside TargetFeature, but everywhere else in the target framework we use TargetFeature.
*** Bug 365136 has been marked as a duplicate of this bug. ***
Tested the target platform UI heavily during today's milestone test pass. Not seeing any problems with the feature management. Verified in I20111206-1015
