One of the most important things we can do with our models is to validate them, testing them against general-purpose and domain-specific well-formedness rules. Last week, we saw how to reuse packages from models stored in a repository in the Papyrus Kepler release.
This week, we take a look at validating models. After all, you wouldn't want to share and re-use packages that aren't up to muster, would you? See a short demonstration video after the break.
The latest code on the cdo_kepler branch in Papyrus SVN evolves the presentation of validation problems in Papyrus beyond Eclipse's workspace resource markers to support annotating model elements in CDO resources (or any other EMF resource, for that matter) with diagnostic information. Essentially, Papyrus implements a modeled analogue of workspace markers in a new friendly UI that better presents the context of problems.
Have a look at the short video above and check out the branch to play with model validation, yourself! Or, wait a few days for the first regular Papyrus nightly build that will actually deliver all of the CDO goodness that we have seen so far. Integration of the branch into the development main-line is in progress as I write this post. See bug 290952 for details of the merge.