Re: [mdt-papyrus.dev] Version Management Errors for Features

[Christian Damus <give.a.damus@xxxxxxxxx>]

Hi, Quentin,

My message was about Oomph’s validation that checks for plug-ins and features that don’t appear to be included in the release because they aren’t contained by any other feature.

The PDE API Tooling has nothing to do with it.  The Papyrus Setup model should already have ensured that PDE won’t complain if an API Baseline is not set, but I encourage everyone to set their baseline to ensure that the tools can help them to keep clean version numbers.  Otherwise, we will have developers continually introducing API and/or version problems that others will have to fix.  I’m sure we would all rather have the tools catch mistakes for us (such as adding a parameter to a public API method) before we push them to the repo.  :-)

So, in short, the better solution to the error about a missing API baseline is to set a baseline, not to suppress the error.

Christian

On 26 February, 2016 at 07:48:46, Quentin Le Menez (quentin.lemenez@xxxxxxxxx) wrote:

Hi christian,

Thanks for the update, I was wondering where this was coming from ! ^^

So are you saying that I should not set the Plugin development > API baseline > Missing API to warning instead of error ?

2016-02-26 13:08 GMT+01:00 Christian Damus <give.a.damus@xxxxxxxxx>:

Hi, Team,

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

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev