Community
Participate
Working Groups
Some of the papyrus models contain dependencies to ui bundles like org.eclipse.ui and org.eclipse.jface. This makes it impossible to use these models in an environment where ui bundles are of no need. A proper separation of model and view would be preferable. One use case is the pre-configuration of a CDO repository with all required papyrus models. CDO allows the installation of packages upon repository configuration therefore the required model bundles need to be present. In a pure server installation environment these papyrus bundles introduce ui dependencies. Adding a simple diagram to a CDO repository adds the following packages which have ui dependencies: org.eclipse.papyrus.infra.viewpoints.configuration org.eclipse.papyrus.infra.viewpoints.policy org.eclipse.papyrus.infra.constraints Others are likely to exist.
This was one of the goals of the big API refactorings in the Neon M5 and M6 milestones, to separate UI dependencies out of "core" plug-ins, especially the models. Perhaps you could check whether the Neon M6 milestone built yesterday meets your needs? These refactorings would obviously not be done in the 1.1.x maintenance branch.
> Perhaps you could check whether the Neon M6 milestone built yesterday meets your needs? M6 will officially be released on next Tuesday (03/29), so you might want to wait for a few days, or use a specific update site (Nightly, or http://download.eclipse.org/modeling/mdt/papyrus/updates/milestones/2.0 )
