| [mdt-papyrus.dev] Version Management Errors for Features |
If you use Oomph to provision your workbench and you don’t import all of the Papyrus plug-in, feature, and releng projects into your workspace as I do, you may find that now plug-in and/or feature projects are marked with errors complaining that they are not included in any feature. This is a helpful hint by the Oomph Version Management tools that it looks like you have installable content that won’t be deployed to the update site and installed by users because it isn’t ultimately contained in a released feature. But, Oomph can’t do the complete validation if it doesn’t have all of the relevant projects in the workspace. To suppress these errors, please do not use the quick-fix to ignore the problems because that will update the version builder configuration in the .project files. Pushing those changes to git would then disable these validation checks for everybody. Instead, configure the level of validation performed by Oomph as shown in the attached graphic, below. Also, I thought I might share how I distinguish API Problems from compilation and other problems. I create a second Problems View instance configured to show just the “API Problems” from PDE and the “Version Problems” from Oomph, and I exclude those from the original Problems View. Cheers, Christian  |