Skip to main content
AgeCommit message (Collapse)AuthorFilesLines
2018-03-11[Releng] [Photon] Delete old Dev framework and add a new Toolsmiths oneQuentin Le Menez1-189/+0
- Delete the old Dev releng profile and replace it with a Toolsmith one - Add new features: Junit, Releng, Diagramgen and Debug to be released - Move the junit framework at the root of the junit test folder - Remove Toolsmiths from the main build as it will have its own - Repopulate the SDK feature and distribute the excess features in theit own root parent - Add a new views feature - Moved the assistants to the toolsmiths folder and put them in the toolsmiths build Change-Id: I1c0331b25607baaf1cfcc635d9c7b0d9c6d73e63 Signed-off-by: Quentin Le Menez <>
2018-03-11Bug 531190 - [Releng] Remove generated tests framework and pluginsQuentin Le Menez1-29/+1
- Remove the generated tests framework - Remove the associated dev plugins and nature to the tests plugins - Remove the xtend files for test generation - Remove the outdated all encompassing test suite - Rewire the dev menu plugin to plain old src instead of src/main/java - Move the junit framework plugins to the root of the junit test folder Change-Id: Id2c0c18762c7c917de93430d3ace2f48940c1297 Signed-off-by: Quentin Le Menez <>
2017-11-08Bug 522500 - [developer] developer feature seems not to be installableFrancois Le Fevre1-0/+6
any more Actions - adding the repository reference to the category - adding the plugin used by tycho to in the pom.xml to reference the needed repository Change-Id: I5957b1a831503e197f2e6272afad79987e2dfd4a Task-Url: Signed-off-by: Francois Le Fevre <> Also-by: Quentin Le Menez <>
2017-09-25Bug 522500 - [developer] developer feature seems not to be installableFrancois Le Fevre1-9/+13
any more Actions -adding the url of gmftooling -adding required plugins after loading developer targetplatform Review -for me we should add all manualUpdate url of /org.eclipse.papyrus/releng/dev/targetPlatform/portable/ Change-Id: I524727cd15cfd6c9181aa8257cb96ff21c84027d Task-Url: Signed-off-by: Francois Le Fevre <>
2017-08-24Bug 520455: [archi] plugin org.eclipse.papyrus.infra.core.pluginexplorerFrancois Le Fevre1-0/+7
seems to belong to developer and not core Actions -move the plugin into the dev folder -move the plugin in to the right feature -rename the plugin according to dev convention Change-Id: I8b4eec213c43eb18591b9a3e817e4a773306cfd7 Task-Url: Signed-off-by: Francois Le Fevre <>
2017-05-05Bug 516243 - [Developer] Remove and .developer.profileBenoit Maggi1-7/+0
from repository - remove both plugins Change-Id: Ie098639ff84cb0093d8c855288bf264552abf112 Signed-off-by: Benoit Maggi <>
2017-04-28Bug 515535: [Interoperability] Move common plugins into papyrus main gitNicolas FAUVERGUE1-0/+4 Add the interoperability common plugins into papyrus main git. Those ones are renamed as: - oep.uml.m2m.qvto.common - oep.uml.m2m.qvto.common.blackboxes - Change-Id: Id17c4fd0e57a5c063c1b4a4e79d833c744f3f61e Signed-off-by: Nicolas FAUVERGUE <>
2017-04-05Bug 514721 - Move org.eclipse.papyrus.uml.developer.mde to oep.toolsBenoit Maggi1-7/+0
repository - remove the plugin from core repository (will be moved in repository) Change-Id: I89b0d8f5b316ac8de2a7a2575da30e8067361aef Signed-off-by: Benoit Maggi <>
2017-03-22Bug 511190 - [devxp] all migration tools are making contribution underFrancois Le Fevre1-0/+7
the root menu -creation of a top developer menu when right clicking to gather all developer plugins menu contribution for popup. Change-Id: Icccebd5114c46ea346e558baad3c0bb281e64721 Signed-off-by: Francois Le Fevre <>
2017-01-12[Releng] [Oxygen] Update the features' descriptions for next releaseQuentin Le Menez1-0/+4
Change-Id: Ic1714265950afb6f16d9b604a47002cc08603c8d Signed-off-by: Quentin Le Menez <>
2016-11-22[Releng] [Oxygen] Update to the new Aggregator fileQuentin Le Menez1-6/+6
Signed-off-by: Quentin Le Menez <>
2016-08-28Bug 443799 - Fix potential bugs identified by FindBugs in oep.infra.*Florian Noyrit1-195/+195
Bug 499554 - Oxygen release version number moved to 3.0.0. Change-Id: I8e112db7175a5b89eb9b37973639627a6c29e007
2016-03-07Bug 488559: [Releng] Projects not included in the Developer Tools releaseChristian W. Damus1-0/+7 Delete obsolete bundles and include the oep.developer.profile bundle in the dev tools feature. Change-Id: I81da098459c758bb3e8d736dd664f3f1d9d4fea5
2016-03-04Bug 472147: [developer]: refactoring of o.e.p.domaincontextcodegen Patrick Tessier1-209/+188
Change-Id: Ica8b08a2523a08cd5421677bc20bf2e8369cbe22 Signed-off-by: Patrick Tessier <>
2016-02-24Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus1-22/+1 Implement version management: PDE API Tooling and Oomph Version Management. Introduce two new plug-in projects to manage versioning using Oomph: * org.eclipse.papyrus.releng.main.release for the Main bundles and features * for the Dev Tools Add new menu actions to the Dev Tools: * main menu bar: * synchronize POM and manifest versions * "Configure" context menu on bundle projects and MANIFEST.MF * optimize bundle dependencies and re-exports * update dependency version ranges to match current workspace and PDE target Remove obsolete menu actions from the Dev Tools: * main menu bar: * Set all Papyrus feature versions * Set all Papyrus plug-in versions * Set versions of all Papyrus dependencies in Papyrus plug-ins Fix versioning errors reported by PDE and Oomph. Ensure proper version ranges consistent with latest build target. Optimize the dependencies of all Papyrus Main bundles and Dev Tools. Remove version- and reexport-checking tests in the BundlesTests that are now not needed because, on the one hand, we now implement discrete bundle versioning (managed by PDE/Oomph) and on the other, we now use re-exports properly to ensure classpath consistency in clients of a bundle's API. Thorough overhaul of the "project editors" API, including: * rationalize the API interfaces * refactor the all-in-one PluginEditor class from the customization bundle to the project-editors bundle * update clients in the Customization and DSML Validation components * fix a bunch of operations that didn't work * add missing operations required by the new Dev Tools actions * complete some unimplemented APIs * add a comprehensive JUnit test suite covering all of the project-editors API Change-Id: I6a699d93909f61099226ceb994140f03ea99a70f
2016-02-22Bug 487480 - Refactor elementtypesconfiguration frameworkFlorian Noyrit1-1/+1
Insert a "oep/infra/types" layer to host the core elementtypesconfiguration framework. Move UML elementtypesconfiguration extensions to "oep/uml" Move EMF elementtypesconfiguration extensions to "oep/infra/emf" Move elementtypesconfiguration tests to oep/tests/junit/plugins/infra/types Rename all elementtypesconfiguration plugins (core, dev, tests and extensions) and corresponfing packages to shorter qualifiers as follows: oep.infra.elementtypesconfigurations -> oep.infra.types.core and oep.infra.types oep.infra.elementtypesconfigurations.edit -> oep.infra.types.edit oep.infra.elementtypesconfigurations.editor -> oep.infra.types.editor oep.infra.elementtypesconfigurations.ui -> oep.infra.types.ui oep.infra.elementtypesconfigurations.invarianttypes -> oep.infra.types.rulebased oep.infra.elementtypesconfigurations.emf -> oep.infra.emf.types oep.infra.elementtypesconfigurations.emf.ui -> oep.infra.emf.types.ui oep.uml.elementtypesconfigurations -> oep.uml.types oep.elementtypesconfigurations.developer -> oep.infra.elementtypesconfigurations.tests -> oep.infra.types.tests oep.infra.elementtypesconfigurations.ui.tests -> oep.infra.types.ui.tests Change-Id: Iad7f5689b183e6ad29daab06a1cc2858ee408aa7
2016-02-05Improve/Fix the support of extensions of theFlorian Noyrit1-0/+7
ElementTypesConfiguration framework - Bug 477206 Change-Id: I50ed9bb1bf6a807881a143875f87c5a6f56a6afc
2016-01-27[Releng] Inclure the UPR Plug-in to the Developer feature to avoidCamille Letavernier1-60/+214
installation issues. Remove an implicit dependency to the UPR update site at install-time Change-Id: I7306fc5c8d4ddc4c6660bef0819e5f460a0f486e Signed-off-by: Camille Letavernier <>
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-08-21[releng] Neon-1.2.0 modification step by stepQuentin Le Menez1-200/+58
Change-Id: I9126d707fecad85c9b5384b35074deba995b6527 Signed-off-by: Quentin Le Menez <>
2015-08-12Bug 464647: [Tests] Generate JUnit tests for diagram view synchChristian W. Damus1-0/+49 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-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-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] Restructure shared test bundles (Framework & BundleTests) to beCamille Letavernier1-0/+4
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-05-22[Developer] Include B3 plug-ins into the developer feature to avoidCamille Letavernier1-0/+21
missing dependencies during installation Change-Id: I0000000000000000000000000000000000000000 Signed-off-by: Camille Letavernier <>
2015-05-22[Developer] Include B3 plug-ins into the developer feature to avoidCamille Letavernier1-0/+14
missing dependencies during installation Change-Id: I2c77810c81164225814c85cef2a9f5d2ec6cdff3 Signed-off-by: Camille Letavernier <>
2015-02-19Bug 460322 - [releng][Developer]Repare broken buildBenoit Maggi1-14/+0
Papyrus-Master-Developer/27/ - Remove oep.documentation from developer build and feature Change-Id: Id183380c88930f84ed1c3a73a2a5f3ac47ef231b Signed-off-by: Benoit Maggi <>
2015-02-08451230: Modeling assistants customization for profilesChristian W. Damus1-3/+9 Infrastructure for dynamically provisionable modeled Diagram Assistants in Papyrus diagrams, based on the element types described by Element Type Configuration models. Includes: - common model for filters - UML-specific filters - Modeling Assistant Providers model - dynamic registry of modeled assistant providers, with extension point for static registrations - GMF modeling assistant provider extension that delegates to modeled providers - Element Type Configurations and Diagram Assistants model generators with wizards, generating models based on UML Profiles targeting specific element-type config models (for a diagram or for UML generally) - Assistants model generation from a GMFGen model for a particular UML diagram - refactoring of JUnit test suite framework for better partitioning of the All-Tests suite-of-suites - automated tests for the filters model, assistants model, assistant provider extension, and model transformations
2015-02-02[Releng] Add developer tools installation to setupChristian W. Damus1-0/+7
2015-02-02458960: [releng][Developer] All dev plugins should be in the buildCamille Letavernier1-0/+7
process - Fix & include infra.emf.commandstack to the build
2015-02-02[Developer Tools - Releng] Add and project.managementCamille Letavernier1-40/+119
plug-ins to the developer build - Add missing dependencies - Fix Java version - Add a dependency to extra-plugins for eclipse.project.editors
2014-09-15[Releng] Update feature versions to 1.1.0Camille Letavernier1-1/+1
2014-08-20[Releng] Update versions to 1.0.1Camille Letavernier1-84/+19
2014-05-22Fix dev feature to remove papyrus.def templatesFlorian Noyrit1-77/+96
2014-04-17[releng] Added the feature for the developer pluginsLaurent Wouters1-0/+86
Change-Id: I4d7614cf009afe26094db3205a4bec19be9a0b42 Signed-off-by: Laurent Wouters <>

    Back to the top