Skip to main content
AgeCommit message (Collapse)AuthorFilesLines
2016-02-08Bug 487442 - Add profile/stereotype support to theFlorian Noyrit2-2/+2
elementtypeconfiguration framework Change-Id: I40493e2b70490fc2a534b5d45bd848ab8957c1cc
2016-02-05checking licence Mauricio Alferez3-184/+109
Change-Id: I194591ff2bbbf084755f22f51cae2fc757415353 Signed-off-by: Mauricio Alferez <>
2016-02-05Improve/Fix the support of extensions of theFlorian Noyrit2-0/+9
ElementTypesConfiguration framework - Bug 477206 Change-Id: I50ed9bb1bf6a807881a143875f87c5a6f56a6afc
2016-02-02[BMM] New feature and releng extra's pomMauricio Alferez2-8/+12
Change-Id: Ia2e7e472e76f28a028005ad196f2ec756a1b54ab Signed-off-by: Mauricio Alferez <>
2016-01-29Improve ElementTypeConfiguration Framework to support:Florian Noyrit1-0/+2
- Advice execution ordering - Prepare Multiple ClientContext in Papyrus Change-Id: I00b5d3d5e090de1b8fc9926c9073913c90dda47e
2016-01-28[BMM] Updating to Papuyrus 2.0. Fixing, moving bmmMauricio Alferez1-11/+6
to its own directory and updating missing extension point to papyrus.infra.core.papyrusDiagram Change-Id: Ia8ccb32b0a31a068f25d3dbed2c0d1f74119889a Signed-off-by: Mauricio Alferez <>
2016-01-27[Releng] Exclude UPR source plug-ins from the Papyrus Dev sourceCamille Letavernier2-1/+32
feature, as the UPR update site doesn't provide sources Change-Id: I2af2874b2abb5da278e8e4a09982910e38d5739c Signed-off-by: Camille Letavernier <>
2016-01-27[Releng] Inclure the UPR Plug-in to the Developer feature to avoidCamille Letavernier2-72/+262
installation issues. Remove an implicit dependency to the UPR update site at install-time Change-Id: I7306fc5c8d4ddc4c6660bef0819e5f460a0f486e Signed-off-by: Camille Letavernier <>
2016-01-22Bug 485220: [Architecture] Provide a more modular architecture (& builds) ↵Christian W. Damus2-6/+6
for Papyrus Refactor the Properties Model bundles into the Infra Layer. The *[.edit,.editor] bundles are renamed as *[.edit,.editor]. The packages within are correspondingly renamed. To support upgrade installation, special p2 update metadata tells the p2 engine how these bundles have been renamed, ensuring proper replacement of the old ** bundles, because otherwise the clash of EMF model registrations would cause run-time errors. The * extension point is moved to * The * extension point has the <context> element moved to a new * point. The <preferencePageBinding> element remains. JUnit tests pass, at least inasmuch as they pass in the nightly builds. Change-Id: I6445808f8eb1144b08c0cd5f0a487d1bad229a4c
2016-01-22Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus9-0/+607 Decouple infra bundles from dependencies on UML, especially for access to the semantic model, using new APIs provided by the ILanguageService and IModel and also by the refined and new implementation of the SemanticService APIs defined in previous releases. Provide generalized access to SemanticEMFContentProviders for the semantic model content in the ModelSet by adaptation of IModels (semantic IModels per new Language Service API) to a new ISemanticContentProviderFactory protocol that creates content providers appropriate to the specific semantic model. Move the identifier of the Papyrus toolbar contribution out of the UML namespace: org.eclipse.papyrus.uml.diagram.ui.toolbar is now just org.eclipse.papyrus.ui.toolbar. Add a new XML enablement expression definition named org.eclipse.papyrus.ui.semanticModelActive as a generalization of the org.eclipse.papyrus.uml.diagram.common.IsPapyrusActiveWithUMLModel for more than just UML Papyrus editors. Tests all still pass (inasmuch as they do in the nightly master builds). Change-Id: I41af229742134428e9e00f41575c14ef1aaf5e09
2016-01-22Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus3-1/+19 Move UI-dependent APIs from the org.eclipse.papyrus.infra.constraints bundle to a new org.eclipse.papyrus.infra.constraints.ui bundle. Replace usage of ISelection and IStructuredSelection in Constraint and ConstraintEngine API methods with Object and Collection<?>, respectively. Move the ElementTypesPreferences class from the infra.elementtypesconfigurations bundle to a new infra.elementtypesconfigurations.ui bundle. For compatibility, it still persists its data via an `IMemento` in the preferences of the core `infra.elementtypesconfigurations` bundle. It implements a new provider extension interface that allows the core bundle's element-type registry to call out to it to get user-defined element types from the workspace. Move the RuntimeValuesEditionAdviceEditHelperAdvice class and some of its attendants from the infra.elementtypesconfigurations.emf bundle to the new infra.elementtypesconfigurations.ui bundle because it needs to open the EditionDialog to let the user edit objects. Likewise the similar APIs in the infra.extendedtypes bundle, including also the entire providers package for action-providers, with the ExtendedElementTypeActionService class, the IExtendedElementTypeActionProvider interface, and the corresponding extension point namespace. Move the ElementTypeValidator class from the bundle to a new bundle. Other fixes for simple inessential UI dependencies and also conflicts in bundle classpaths (such as in the Sequence Diagram particularly) that cause deadlocks in class loading in a complete Papyrus environment, such as the AllTests suite. Factor the UI dependencies out of the infra.onefile bundle into a new infra.onefile.ui bundle. Tests all still pass (inasmuch as they do in the nightly master builds). Change-Id: I43510c84f54c3e0e52cd7d2aa3ca6aca95b894a7
2016-01-22Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus10-4/+609 Move UI-dependent APIs from the org.eclipse.papyrus.infra.emf bundle to a new org.eclipse.papyrus.infra.ui.emf bundle. Accordingly move tests into a new org.eclipse.papyrus.infra.ui.emf.tests bundle. Now that we have an UI EMF bundle, move the editor-page advices from the infra.ui bundle into it, which is a more appropriate home for them. One UI dependency is removed by reordering of code in the EMFHelper::getEObject(Object) API: * the EMF Facet tree elements are once again IAdaptables, providing their encapsulated EObjects or EReferences as adapters. So, the case handling IAdaptable is moved ahead of the test for is-an-EObject because these tree elements are also EObjects but are not interesting in themselves Also, the dialog-settings for the EMF Facet customization manager are moved into the infra.ui.emf bundle, as is the lazy initialization of the manager from those settings. Clients are refactored to get the customization manager from this new bundle (via a new ProviderHelper API) to ensure this lazy initialization. Various UI-dependent ServiceUtilsForXyz classes that were in the infra.emf bundle but had nothing to do with EMF are moved into the infra.ui bundle. UI-dependent classes from the org.eclipse.papyrus.infra.emf.readonly bundle are moved into the org.eclipse.papyrus.infra.ui.emf, also. These include extraction of the editor reload listener from the ReadOnlyManager class by means of a new general-purpose IReadOnlyManagerProcessor OSGi service interface. Tests all still pass (inasmuch as they do in the nightly master builds). Change-Id: Ieb0993b2ed1a7a49890d3471c7b42bc4f218fec6
2016-01-22Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus3-3/+9 Move UI-dependent APIs from the bundle to org.eclipse.papyrus.infra.ui. Accordingly move tests into a new org.eclipse.papyrus.infra.ui.tests bundle. Two crucial UI dependencies are inverted by introduction of new OSGi services with core interfaces specified in the non-UI layer: * IExecutorService extends Java Platform's ExecutorService with APIs for synchronous execution (a la Display.syncExec). A new CoreExecutors class in the bundle supplies the instance provided by the OSGi service implementation in the infra.ui bundle. This provides compatibility for clients of various UIUtil APIs that they can no longer access * IContextualServiceRegistryTracker abstracts the concept of the default ServicesRegistry found in the currently active editor, which the ServiceUtilsForHandlers class (and hence all of its clients) relies on. Again an OSGi service implementation in the infra.ui bundle supplies the implementation of this tracker, which is exposed in infra.core through the service-utils API Also move UI-dependent APIs from the org.eclipse.papyrus.infra.core bundle into org.eclipse.papyrus.infra.ui. This includes * moving the 'papyrusDiagram' and 'papyrusContentOutline' extension points into the org.eclipse.papyrus.infra.ui namespace * moving various UI-related services such as EditorLifeycleManager, SaveLayoutBeforeClose, and the IMultiDiagramEditor, itself, into the org.eclipse.papyrus.infra.ui bundle This necessitates not only widespread refactorings on the moved APIs, but also concomitant move of other APIs in other bundles because they cannot plausibly use these moved APIs from their new home in org.eclipse.papyrus.infra.ui and/or they cannot reasonably also be moved to the UI bundle and/or they must be used by bundles that now have no UI dependency: * the DI/sash-windows EMF model is moved out of infra.core.sasheditor.di bundle into a new model-only org.eclipse.papyrus.infra.sashwindows.di bundle (which symbolic name incidentally now better reflects the contained Java package names) * the IPageManager and ILocalPageService interfaces are moved out of infra.core.sasheditor.di bundle because they need to remain accessible by headless code such as the edit advices that ensure deletion of sash-model pages for notations that are deleted. These are now in a package named org.eclipse.papyrus.infra.code.sashwindows.di.service. Accordingly the class hierarchy implementing the IPageManager interface is changed: the obsolete PageMngrImpl is deleted, replaced by a BasicPageManagerImpl which now the PageManagerImpl extends. A service factory creates the basic page manager in a headless context, but is overridden by the UI-aware implementation when the UI bundles are installed * the MultiDiagramEditorGefDelegate (which has a GEF 3 dependency) is moved from the org.eclipse.papyrus.infra.core.sasheditor bundle to a new org.eclipse.papyrus.infra.gmfdiag.gef bundle. Its usage for an adapter of ActionRegistry type is extracted out of the CoreMultiDiagramEditor class into a new external adapter-factory in the infra.gmfdiag.gef bundle Tests all still pass (inasmuch as they do in the nightly master builds). Change-Id: I573dee5d9312d6e5746d74575350d0152b591ab3
2016-01-18Bug 484701 - [QDesigner] Refactoring - code generators, architecture ↵Ansgar Radermacher1-0/+7
exploration and component based design should be organised in common directory Add missing oep.qompass.ui to codegen feature
2016-01-17Bug 484701 - [QDesigner] Refactoring - code generators, architecture ↵Ansgar Radermacher18-67/+824
exploration and component based design should be organised in common directory Bug 478797 - [model library] Decide which model library to use for C++ primitive types Change-Id: Idade4edfcf803da3528c0873aa04b754915866fd
2016-01-12[BPMN] Include collaboration diagram plugin in feature and build andJuan Cadavid2-1/+9
about.html in src build Change-Id: Ie343537d76632c0507ae60b1e66f0052aa4615d1 Signed-off-by: Juan Cadavid <>
2016-01-11Bug 484419 - [Extra-plugin]Create EFFB Diagram Patrick Tessier7-0/+619
commit for the master Change-Id: Id77f5a0886282c2b5139c6263a5a18d1c0dad53a
2016-01-07[Manufacturing] Include licence files in for theJuan Cadavid1-2/+4
feature Signed-off-by: Juan Cadavid <>
2016-01-07[Manufacturing] Fix build configurations for the source buildJuan Cadavid1-0/+1
Signed-off-by: Juan Cadavid <>
2016-01-04[Manufacturing] put in the buildJuan Cadavid1-1/+2
Signed-off-by: Juan Cadavid <>
2016-01-03[Manufacturing] RAMI 4.0 model templateJuan Cadavid10-30/+754
Signed-off-by: Juan Cadavid <> Setting up Papyrus4Manufacturing feature Change-Id: Ibdf89968061d1d53544cb06c003219782865e7c3
2015-12-09Bug 469188: [Editor] Page management improvements in the Papyrus multi-editorChristian W. Damus1-2/+0 Present all notation views (diagrams, tables, etc.) in a single list instead of separate lists in the welcome page.
2015-12-08Bug 469188: [Editor] Page management improvements in the Papyrus multi-editorChristian W. Damus1-0/+4 Test suites for the core Welcome Editor service and related components and for the Diagrams table content.
2015-12-08Bug 469188: [Editor] Page management improvements in the Papyrus multi-editorChristian W. Damus3-0/+8 This is a squashed commit comprising all of the changes on the committers/cdamus/469188-editor-welcome branch for the introduction of a Welcome Page in the Papyrus Editor. commit 51d64a198c2069b208b5231212a5514441514c54 Implement drag-and-drop rearrangement of the sections in the simple grid-wise layout of the Welcome Page. Persist the user's customization in the sash/di resource with the sash model, using new classes in the Welcome package. commit b59f057cf1e08b51942aac1f45226a304c48039e Fix enablement condition for Show Welcome Page action which has been broken since the page was changed from an editor to a plain composite. commit 69cee20b44c699c6a078e66bf9b16a83c1de7315 Remove the databinding properties APIs for Forms widgets that are no longer needed since the NatTable refactoring of the Diagrams table in the welcome page. commit 00cfdd106421c0b1366c2a7deade819b4a3041ef Add table of languages to the General section in the welcome page. Add section of hyperlinks to related views to the welcome page. Implement ordering of the contents of the welcome page according to tab 'afterTab' relationships and priorities. Overall the layout is still two rows with a variable number of columns. commit a7d739b8e03bea5d4cf5e4d0d3663adbc62f5018 Let the SashModel report to listeners when its storage mode changes so that the two different UI presentations of that mode can remain up-to- date at all times. commit 7fc4f8bf1f0fcee31f84b976e29cd7b3848ec47d Ensure that new models initially track the active page of each tab folder because they store their layout privately by default. commit 6d5dbf27a4428645655bcf6ff9a99d4a3c77dcb8 Implement optional tracking of the active page in the private sash model and switching between private and shared storage of the layout. Includes: * enhancement of the Sash DI model to include a currently selected page for each tab folder and a boolean flag whether to restore the last selection in each tab folder * a new editor lifecycle event for "pre display" to provide a hook to set up the page activation before the SWT controls are rendered, so that the editor doesn't open up and then change page selections while the user watches * expose the SaveLayoutBeforeClose behaviour for re-use when changing layout options in the welcome page * update enablement from editable-ness for Properties widgets that force refresh commit 97897b3d0d295a71a7173a584ceda3ac24c5c6ea Factor out some more common bits into core plug-ins (e.g., the IsWelcomeElement constraint in the properties environment). Create the list of tables in the welcome page. This requires some renaming of properties model content in the diagrams list for disambiguation. commit f73fe34e87c915cc603ec12c608c020406ea7d73 Refactor the Diagrams table as a reusable NatTable of hyperlinks. commit a6308f25a8c6e6c129174e9c418cb90e6f025e16 Move the column headers of the diagrams table out into a separate composite that does not scroll vertically with the table of hyperlinks (though it does track the table's horizontal scroll position). commit 0425bf34630e4420db3674fa8d4641820a305478 Add a separate preference page for Welcome Page Content. This depends on a new extension in the context registry for association of contexts with preferences pages (by default, associating legacy contexts with the Properties View preference page). commit 06719c107a3f323be53ca6ada4f820f2d4ef10cb Rework the contribution of welcome-page content to: * eliminate the custom extension point for section providers * use the Properties View framework to obtain welcome-page sections for the Welcome model element Update the Diagrams table provider as a property section for the Welcome model. This involves implementation of a custom table-of- hyperlinks widget. Several reusable data-bindings classes are added to the appropriate Papyrus infra-layer bundles. commit 4069f62cc89413b8739cc6c33211ac5a11942bc4 Welcome page content for diagrams. commit 8599ee6bdf7b2c7423811fee3e2441a618621ce4 The Welcome Page doesn't need to be an editor, just a composite. So, let any page part (including simple composites) be optionally closeable and change the WelcomePage into a simple composite part instead of a nested workbench editor-part. commit 83b581ea9aadb5b852b36b2fa0524ca7df60b255 Initial definition of an extension point for welcome section providers. commit f949eaf6cf131449f4584b71072033b22cd1cea2 Initial implementation of a (so far, empty) Welcome page that is always open when no other Papyrus editor pages are open. Change-Id: I351118dc0b6a0dea505719a8c62ef430c273c7cf
2015-12-04Bug 477384: [Canonical] Should not use drop requests to create viewsChristian W. Damus1-0/+2 Changes to core APIs to remove PapyrusCanonicalEditPolicy's dependence on the generated diagram drag-and-drop behavior: * extract the CommonDiagramDragDropEditPolicy's abstract API for information about diagram-specific view types into a new service * update the canonical edit-policy and diagram-to-diagram synchronization infrastructure to use the new VisualTypeService to obtain information about the diagram's specific view types to then let the view service create views without resorting to drop commands * update extensions of various canonical strategies in the UML diagrams to adapt to the new drop-free synchronization mechanism Update the Papyrus Diagram GMFGen extensions and code generation templates to add generation of the IVisualTypeProvider that plugs into the new VisualTypeService to support canonical synchronization and drag-and-drop. Includes regeneration of the GMFGen extension model using EMF's most recent templates, which result in minor changes to most model source files. Regenerate all UML diagrams to create and register the visual type provider extensions. Also update the BREE for diagrams to 1.8 because at least one of them requires Java 8 to compile properly. * Note that the interaction overview diagram uses a code generator that is not published on, so I had to emulate the code generation step for this one * Note also that the SysML 1.1 diagrams likewise cannot be re-generated but, moreover, they do not implement the common pattern for Visual ID Registry, so they are also updated "by hand" for parity with the Mars implementation of drag-and-drop (which had gaps) Deprecate the ICreationTargetStrategy extension API which was only needed to redirect drag-and-drop requests, but these are no longer employed in the canonical synchronization. Also some fixes for region layout problems in the State Machine Diagram: * update custom creation edit policies to re-use the commands used by drag-and-drop and untargeted creation that perform initial placement of new regions * fix the GMFGen to register the custom creation edit policy for the state machine compartment Change-Id: I3afc68d6f0f1bfe05e336c9138a7f1acbc8f643b
2015-11-26bug 482611: [Table] Papyrus must provide an API to manipulate the table - ↵Vincent Lorenzo1-16/+43
provides the API Signed-off-by: Vincent Lorenzo <>
2015-11-24[Releng] Update feature name and P2 Site for consistencyCamille Letavernier1-1/+1
- Add BMPN sources to the Extra P2 Repo - Prefix the Revision Tool feature name with Papyrus Change-Id: Ia70a970efcc01d8ab0340e0d8823879e8d5e267b Signed-off-by: Camille Letavernier <>
2015-11-18[BPMN] License FixJuan Cadavid1-71/+2
Signed-off-by: Juan Cadavid <>
2015-11-17Bug 481686 - [Moka] End migration by removing source from the main repoBenoit Maggi11-641/+0
- remove all resources related to moka - new repository : Change-Id: Ie187cc32fadd83e33dc9b345a6f159765f28c46f Signed-off-by: Benoit Maggi <>
2015-11-10Bug 481377 - [Extra plugins][Req] The assistant shall support theMauricio Alferez1-0/+7
creation of initial profiles based on class diagram - New plugin req.domainModel2profile - New submenu in PapyrusReq called "Tools to define requirements profile" with two entries: "Define or Update Stereotype and Profile on Demand", and "Generate Profile from Domain Model". --- - I updated the org.eclipse.papyrus.req.feature to include the new req.domainModel2profile plugin and the pom.xml files. - I also took the time to correct comments and typos. Change-Id: Id829cd3dad789e691f1164af89463f8afbeb72e9 Signed-off-by: Mauricio Alferez <>
2015-10-31[Extra plugins][Req] Wrong feature descriptionMauricio Alferez1-90/+90
Change-Id: I7a0573c818b4055375e6630380cec32b3cdc7514 Signed-off-by: Mauricio Alferez <>
2015-10-15[Extra plugins][Req][BMM] Adding BMM to papyrus extra update siteMauricio Alferez8-0/+738
Change-Id: Ide7a4d21fd890561702a105bf0101156a093a740 Signed-off-by: Mauricio Alferez <>
2015-10-01add oep.uml.diagram.linklf to the buildVincent Lorenzo1-54/+196
2015-09-29467521: [Model Import - RT] Update the Model Import to target Papyrus-RTCamille Letavernier1-7/+0 - Remove the PapyrusRT profile from the feature, and add it to the update site Change-Id: I20639ee9d243bab289ea8142081cff6d86e40d26 Signed-off-by: Camille Letavernier <>
2015-09-11467521: [Model Import - RT] Update the Model Import to target Papyrus-RTCamille Letavernier1-4/+26 - Add the PapyrusRT Profile plug-in to the Model Import feature Change-Id: I170d43ddaa36e387b242ca9f5bebcb3ae7f4f30d Signed-off-by: Camille Letavernier <>
2015-08-21[releng] Neon-1.2.0 modification step by stepQuentin Le Menez190-5137/+3305
Change-Id: I9126d707fecad85c9b5384b35074deba995b6527 Signed-off-by: Quentin Le Menez <>
2015-08-20Bug 475373 - [SysML 1.4] Remove remaining elements from core repositoryBenoit Maggi7-620/+0
- remove Neon oomph config for SysML 1.4 - remove all elements related to SysML 1.4 Change-Id: I36b31b4af87d8813417c2c3a313438cbb58f1fb5 Signed-off-by: Benoit Maggi <>
2015-08-19Bug 474610: [Profiles] Papyrus does not detect out-of-date profile applicationsChristian W. Damus1-0/+8 Fix the determination of out-of-date profile applications by comparing Ecore definition package URIs instead of their namespace URIs, which can be expected to be the same for multiple versions. Includes JUnit test cases covering: * UML2-style local dynamic profiles with always the same NS URI * Papyrus-style local dynamic profiles with always the same NS URI * UML2-style registered dynamic profiles with always the same NS URI Change-Id: Ib4ed3cbd44115787417713a6c3fb7b27e3ffd264
2015-08-12Bug 464647: [Tests] Generate JUnit tests for diagram view synchChristian W. Damus3-0/+77 Adaptation of initial prototype of a Papyrus Tests Generation framework to add diagram synchronization tests. Changes by Christian W. Damus <>: Rebase onto latest Mars maintenance branch. Fix .ignores: ensure that only contents of xtend-gen/ folders are ignored, not the folders themselves Convert Xtend codegen templates to UTF-8 encoding Update the QVTo transformation to support the statically generated UTP profile. This requires: - invoking the UMLResourcesUtil API for stand-alone set-up - updating the profile-registration workflow component to support the registration of a statically generated profile - updating the QVTo transformation to ensure that applicable stereotypes are resolved in the proper ResourceSet context to avoid losing all applied stereotypes in the generated test model. This, in turn, requires a Java black box to handle the EMF-specific concerns of resource-set context that QVTo is not aware of Fix files to include all sources and POMs to generate sources in xtend-gen/ folder. Fix compilation problems in the integration of the generated tests into the master suite bundle. Update the Tycho build to include the test generation framework bundle. Update the build and Oomph setup to include the UPR profile bundle dependency and the Papyrus Developer tools dependency. Fix numerous codegen problems: - base model does not reflect correct package name for palette tests - inject replaceable templates instead of making them all static - add generation of import statements in suites - fix references to test constants interface - fix references to diagram creation command Fix remaining compilation errors in Use Case tests: - look up the DiagramUpdater class to compute correct import - factor out creation of generated files into an utility extension - factor out generation of the copyright header comment - add some imports to templates that were missing them Refactor Xtend codegen templates to: - improve management of imports - improve names of AllXyzTestsGen suite classes - don't generate test classes that have no test cases - share common code to simplify the specific test case templates Fix more code generation problems: * missing package imports for required edit-part classes * invalid package imports (non-existent edit-part classes) * non-conformant names of diagram creation command and test constants interface. This introduces new attributes to test classes in the model, of String type, specifying the relevant type names. The defaults are computed by the QVTo transformation but may be overridden (hard-coded) by a diagram test's bundle's specific QVTo to provide custom names Add generated tests for Communication Diagram. Fixed workflow infrastructure to support all-tests generation. Use URI mappings to eliminate the need to copy and delete the framework's QVTo files. Add an infrastructure for generation of diagram synchronization tests. This includes * new abstract test classes in the oep.uml.diagram.tests bundle * updates to the framework UML model to capture the new base test classes * new QVTo transformation to generate synchronization tests in the UTP model * new Xtend template to generate synchronization tests from the UTP Fixed various small problems: * unwanted newlines in some test method bodies * fully-qualified references to UMLTypes class in synchronization tests * missing commas in QVTo scripts that cause edit-part names to be concatenated * (a biggie, actually) fix the all-tests generation to avoid repeating all previous transformations at each step Translate QVTo transformation steps to Xtend: Xtend exposes list values in UML models in their native EList terms, which affords stable and predictable ordering of transformation operations and, hence, test model structure and generated code. It also provides for more concise, debuggable, searchable, and performant transformations with better Java integration. Assign predictable, stable XMI identifiers to elements of generated UML models to avoid unnecessary diffs in source control when re-generating. Regenerate code from the Xtend version of the framework. Git-ignore the generated UTP source models because they reference and depend on UML instance models of the GMFGens that are already git-ignored, so there's no point in having these in git. Besides that they are now much larger because of the generated unique XMI IDs. Develop a DSL for compact and readable declarations of transformation rules for test contexts and assembly into packages. This uses new active annotations which, owing to a logistical limitation of Xtend, must be defined in a new separate plug-in project. Finally! Fixed the generation of the wrong diagram-updater instance field reference for Sequence Diagram, which as a legacy diagram still uses TYPED_INSTANCE. This employs a class-file scanning hack that is potentially expensive in I/O, so it uses a new @Cached active annotation that caches method computation results. Complete the specification of generation of view synchronization tests, adding the following scenarios: * synchronize child label nodes in label compartments of top shapes * synchronize child shape nodes in shape compartments of top shapes * synchronize connections between shapes * synchronize connections between shapes where the source owns the semantic link Define a new ClassificationSuite JUnit test runner that supports filtering entire suites by classification annotations. Apply this runner with the @GeneratedTest annotation to all generated test-suite classes. Refine the generation of link creation and synchronization tests to test links only between edit-parts that the GMFGen model reports as valid sources and targets for the links. This vastly reduces the number of invalid test cases generated for elements that cannot be linked (such as Include between an Actor and a Package). Integrate code generation into the build (both maven build and Eclipse workspace) and suppress generated sources from source control. This is implemented as a build profile in a new parent POM for the UML Diagram Tests bundles. Further elaboration and fixes: * rename 'edition' tests as DirectEdit in generated tests (not yet in the framework) * use a generic name for the test class for top node creation from palette * fix test cases for creation of links in containers to actually create the source and target elements in such container * fix the ClassificationConfig to drill into test suites to look for further filtering annotations instead of assuming that the entire suite is a 'standard' test when the 'standard' tests are excluded by the requested configuration * split test cases that execute multiple test scenarios into separate test case methods per test scenario. This ensures that a single test failure doesn't hide several other test results * move @GeneratedTest annotation from test case method to the test context class to reduce overhead of annotations in the VM * use the GMFGen model's information about child node containment to avoid generating all permutations of top-node/child-node, eliminating most of the the invalid child-node creation tests * fix broken references to the UML model for the Ecore metamodel in UML models for the gmfgen and genmodel metamodels by redirecting them to the UML2-provided Ecore metamodel. Delete the obsolete local ecore.uml * define a model of test exceptions for the purpose of constraining the generation of the UML-UTP model to exclude unwanted permutations of edit parts, optionally for specific kinds of tests * enhance the UML-UTP test model generation to filter the tests that it would generate through the optionally provided test exceptions models * add a test exclusions model to the Use Case test bundle to exclude tests for package-import relationships on classifiers (which UML supports but the diagram does not) * generate a CSS stylesheet (attached via an annotation on the test context class) to enable synchronization of the diagrams for tests * fix generation of invalid child-node permutations in the synchronization tests by using the compartment container information in the GMFGen model * fix various bugs in the abstract test framework operations found by running the generated tests Further refinement and fixes: * add some more flexibility to test exceptions model and utilize it for exclusion of some more Class Diagram tests that don't make sense or cannot be generated like the rest * simplify the generation of synchronization tests, removing the specialized M2T templates * fix the deletion tests that failed because the edit-part to be deleted was not selected * fix the tests dealing with child label nodes in nodes that are themselves child nodes by ensuring proper creation of a top-level node to contain the nested node that has the label children * fix abstract appearance test cases, resolving a large proportion of test failures * further simplification of the M2T templates based on structure of the UTP model * don't just not generate excluded tests, but apply the @FailingTest, @NotImplemented, and @Ignore annotations as appropriate to the reason for the test exclusion * now that the UTP model is not managed in source control, it can use generated XMI IDs to save some space (the computed unique IDs were long, based on qualified names) * add another kind of test exception that blanket excludes an edit-part from all tests * add support for completely omitting test cases from the generated code (instead of just annotating them), e.g. for cases where the generated code would not even compile * create a DSL embedded in the transformation workflow for definition of test exceptions, as a convenient and integrated alternative to the test-exceptions model * add default calculation of edit-parts-to-test lists for all kinds of tests, to stream-line the workflow model. Employ this with the new test-exceptions DSL in the Use Case Diagram tests generation workflow as an example of how it all works * further streamlining of the test exceptions DSL with an active annotation generating constants for the reason kinds and multiplicative nesting of edit-part blocks in forbidden permutation rules * adopt the test exceptions DSL in the Class Diagram tests * support injection of custom GMFGen-to-UTP transformation rules * customize the link creation tests in the Class Diagram to fix association link failures caused by odd default name that associations get in the test environment * automatically compute imports for all edit-part classes actually required by the tests, based on the references to edit-parts in the generated activities, to avoid unused import warnings for edit-part classes that would only have been used by tests that were excluded * fix some problems in behavior diagram tests that failed on attempting to create the top container frame (behavior) that was already implicitly created by creation of the diagram * update abstract synchronization tests to take advantage of diagram editor sharing (cherry-picked from streams/1.1-maintenance Id627299a0b28614877cba0e372d980c6bf3ec675) Signed-off-by: jcadavid <> Signed-off-by: Christian W. Damus <> Change-Id: I59cc3d621889f0caeff78acd6c0eb07c7479268f
2015-07-16Papyrus BPMN customizationJuan Cadavid9-120/+869
Change-Id: Ifccfedbbd4f30f166e1b39136ec1822a63f4f33c Signed-off-by: Juan Cadavid <>
2015-07-03Bug 471836: [DevTools] The oep.uml.developer.mde plug-in should be in the ↵Christian W. Damus1-1/+8
developer feature Add the developer documentation modeling plug-in to the developer tools feature. Also fix the generation of wiki text to calculate the selected model's project so that it doesn't fail on every attempt to generate. Change-Id: I22eae620ae8707bcc9fb113b158046a6ff4e0d72
2015-06-19470582 - [QDesigner] The plugin oep.qompass.designer.cpp should be part of ↵Ansgar Radermacher1-0/+7
the Qompass basic feature
2015-06-15[Releng] Remove invalid plug-in from developer featureCamille Letavernier1-7/+0
- Remove invalid plug-in from developer feature - Remove EPF RichText modules Change-Id: I1c4c3fafb71f9b39a2befc9d658a775bb15a536d Signed-off-by: Camille Letavernier <>
2015-06-12[Releng] Fix license & typo in the new JUnit Framework featureCamille Letavernier3-10/+143
Change-Id: Ib1bb50c33a5d2c79741eeca6bd784efde49dee1f Signed-off-by: Camille Letavernier <>
2015-06-12[Releng] Restructure shared test bundles (Framework & BundleTests) to beCamille Letavernier7-0/+491
able to use them in any Test Builds - oep.junit.utils, oep.junit.framework and oep.bundle.tests now belong to the Papyrus Developer build Change-Id: Ibd98199e93e62eca6ff43d58bf7de142193ba9fb Signed-off-by: Camille Letavernier <>
2015-06-12[Releng] Remove oep.eclipse.project.editors from an extra feature (MovedCamille Letavernier1-2/+0
to main) Change-Id: I0000000000000000000000000000000000000000 Signed-off-by: Camille Letavernier <>
2015-06-12[Releng] Remove oep.eclipse.project.editors from an extra feature (MovedCamille Letavernier1-24/+32
to main) Change-Id: I0421054bd3d5644476840f5b93c361561cb38dc0 Signed-off-by: Camille Letavernier <>
2015-06-11469953: [Releng] Update the build to support a global POMCamille Letavernier93-181/+198 Change-Id: I050cf9dbbdd5705aaf8d45f2db3458226d148002 Signed-off-by: Camille Letavernier <>
2015-06-10Fix Diagram Definition Feature included pluginsFlorian Noyrit2-10/+9
Change-Id: I83be84623543753c044c9f9cc78e6fc4c2240e7c Reviewed-on: Reviewed-by: florian noyrit <> Tested-by: florian noyrit <>
2015-06-10[Releng - StereotypeDisplay] Add the StereotypeDisplay Table to theCamille Letavernier1-65/+72
feature Change-Id: Ica06b6d10bf2153f535d58a83505dc08186b16bd Signed-off-by: Camille Letavernier <>

Back to the top