Skip to main content
aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2016-04-08Bug 491332: [Version Management] New API breakages since 1.1.xChristian W. Damus1-1/+1
https://bugs.eclipse.org/bugs/show_bug.cgi?id=491332 Fix/suppress some cases that have trivial resolutions. Change-Id: I3b45fda78448000c923635bdbb808709d8cffa89
2016-04-07Bug 491233 - [Navigation] Next and previous diagram buttons should be inShuai Li3-1/+1
Eclipse navigate toolbar and should be green Change-Id: Ifb3921ec73fad62bd1fc7b73cef3d152483118ba Signed-off-by: Shuai Li <shuai.li@cea.fr>
2016-04-06Bug 407733 - [General] Papyrus shall support navigation history withShuai Li4-56/+262
back and next buttons - Update for post-refactoring Neon Change-Id: I23a0a26449c2bda1e162d07e659680bea218ebcd Signed-off-by: Shuai Li <shuai.li@cea.fr>
2016-03-06Bug 489075: [DevTools] Manifest editor reorders main headers on saveChristian W. Damus1-4/+223
https://bugs.eclipse.org/bugs/show_bug.cgi?id=489075 Ensure that the manifest file is rewritten with all headers in the original order, including additional sections beyond the main section. Also fix problems of empty sections being left after all their attributes are removed and new sections not being added when setting their initial attributes. Change-Id: I1aec074a15b61dc3048883aee8b748938e11f78c
2016-03-03Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus3-0/+294
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220 Complete the configuration of PDE API Tooling in the Papyrus Main and Developer Tools projects, including: * adding the API Analysis nature and builder to .project where it was missing * adding a new menu action in the dev tools Project Management menu to ensure that all Oomph version-management projects in the workspace have API analysis also * fixing API version analysis problems, mostly by upversioning bundles to 2.0 but also applying API filters in some cases where it seems appropriate * implementing project-level API Analysis preferences for warning severity of missing @since doc tags (the default is error) and adding it to the Oomph project preferences management Change-Id: I3f5fad20ffc7bb66eec0abbb86b5cc52aacb1ff1
2016-02-24Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus31-1054/+2021
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220 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 * org.eclipse.papyrus.releng.dev.release 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-13Revert "Bug 485220: [Architecture] Provide a more modular architecture ↵Christian W. Damus3-7/+3
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220" This reverts commit f050d4119a2316b27588076d4fc90152773fc019.
2016-02-13Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus3-3/+7
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220 Fix build failure to resolve bundles in referenced p2 repositories by restoring the missing <groupId> elements in the POMs which, as it turns out, are not inherited from the parent module, despite what the m2e validator says. Change-Id: I62dacc9c70c940d28c3c02e1e35c8f874a7d3df0
2016-02-12Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus30-6/+4131
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220 Factor UI dependencies out of the UML Element Types bundle. This includes moving some advices that interact with the user into a new org.eclipse.papyrus.uml.service.types.ui bundle. Pull up the PasteCommandService and IPasteCommandProvider API into the Infra Diagram layer where the extension point is defined. Deprecate the old API in the UML layer. Introduce a service for participation of languages in CSS styling: * styling reset actions in the Reset Style command * access to semantic model classes and properties to make available to CSS Factor PapyrusObservableValue and cohorts out of the UML Tools bundle into the Infra Layer for more general reuse and to relieve the Diagram Infrastructure layer of UML dependencies. The old API remains as deprecated. Remove the Infra Diagram Layer dependency on UML Layer for property testers governing deletion in the diagram. Includes introduction of a new IGraphicalDeletionHelper OSGi service for delegation of the determination of whether an element can be deleted from the diagram and replacement of the XML expression properties * org.eclipse.papyrus.uml.diagram.common.isSemanticDeletion * org.eclipse.papyrus.uml.diagram.common.isReadOnly by * org.eclipse.papyrus.infra.gmfdiag.common.isSemanticDeletion * org.eclipse.papyrus.infra.gmfdiag.common.canDelete (where the latter is the negation of the property that it supersedes) Extract UML dependencies from the Diagram Outline and CSS Editor bundles. Remove unused MDTUtil APIs that referenced a UML-specific annotation. Move the Diagram Infrastructure CSS Palette bundle into the UML layer because it serves to provide extensions on the Palette Service, which is an overtly UML-specific capability. All client APIs for the Properties View are moved from org.eclipse.papyrus.views.properties bundle to a new org.eclipse.papyrus.infra.properties.ui bundle. This includes renaming of: * extension points * label-provider contexts * XWT namespaces Add an "all UI tests" suite. Define a componentized hierarchical build layout of the main plug-ins Change-Id: I43f8f3644857a18b69715f5a2f1da9b1cf286d67
2016-01-22Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus1-1/+1
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220 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. Damus2-2/+2
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220 Move UI-dependent APIs from the org.eclipse.papyrus.infra.tools 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 infra.tools 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
2015-10-16Bug 471697 - [Navigation] Toolbar buttons to go to next/previous diagramShuai Li3-0/+39
in active window - Toolbar contributon Change-Id: I6d102749f384d666fd3d28d81f03ef6844d771be Signed-off-by: Shuai Li <shuai.li@cea.fr>
2015-08-21[releng] Neon-1.2.0 modification step by stepQuentin Le Menez3-15/+11
Change-Id: I9126d707fecad85c9b5384b35074deba995b6527 Signed-off-by: Quentin Le Menez <quentin.lemenez@cea.fr>
2015-06-11469953: [Releng] Update the build to support a global POMCamille Letavernier1-2/+2
https://bugs.eclipse.org/bugs/show_bug.cgi?id=469953 Change-Id: I050cf9dbbdd5705aaf8d45f2db3458226d148002 Signed-off-by: Camille Letavernier <camille.letavernier@cea.fr>
2015-04-23Bug 465122 - [Navigation] Keys to travers opened tabs in editorShuai Li4-25/+202
- Remove unnecessary execute methods - Log errors - Fix wrong javadoc - Modifications after review. Most noticeable change is that multi-tabfolders are now supported, i.e. traverse tabs in the current active tabfolder. - Add getNextPage and getPreviousPage methods in ISashWindowsContainer and SashWindowsContainer (implementation) - Add CollectNextPageVisitor in SashWindowsContainer to collect the next/previous page - Extend org.eclipse.ui.bindings with 2 key sequences: CTRL+TAB and CTRL+M2+TAB triggering commands below - Extend org.eclipse.ui.category.navigate with Next Tab and Previous Tab commands - NextTabHandler and PreviousTabHandler (extend TraversTabHandler) for the commands Change-Id: I56f0ac57dcb62540a3b5ddf9bb2e21568f20b9f3 Signed-off-by: Shuai Li <shuai.li@cea.fr> Reviewed-on: https://git.eclipse.org/r/46192 Tested-by: Hudson CI Reviewed-by: Christian W. Damus <give.a.damus@gmail.com> Tested-by: Christian W. Damus <give.a.damus@gmail.com> Reviewed-by: Benoit Maggi <benoit.maggi@cea.fr>
2015-03-23Bug 462256: [menu]: migration of main menu inFrancois Le Fevre - CEA2-20/+2
org.eclipse.papyrus.infra.ui Change-Id: I1cac9421f36ec5bc20b2e1d7c08c27422571fe21 Task-Url: https://bugs.eclipse.org/bugs/show_bug.cgi?id=462256 Signed-off-by: Francois Le Fevre - CEA <francois.le-fevre@cea.fr>
2015-02-11Bug 459566: [Releng] Consider letting Tycho use JDT's project settings for ↵Christian W. Damus3-8/+16
compilation https://bugs.eclipse.org/bugs/show_bug.cgi?id=459566 Add Tycho compiler's <useProjectSettings> to the plug-in management in the main top POM to ensure that each project's build preferences are respected. This does require removing a few {@link}/@see references to restricted API in doc comments to work around a bug in Tycho (459554). A great many plug-in projects using 1.6 source constructs (mostly @Override of abstract methods) failed to declare 1.6 requirement either in the BREE, or the classpath/compiler settings, or both. Change-Id: Ia73b592fff8d46eaf0bc628b6e21d1e758ff0c64
2014-09-15[Releng] Update feature versions to 1.1.0Camille Letavernier1-2/+2
2014-09-15[Releng] Change plug-ins version to 1.1.0Camille Letavernier2-6/+6
2014-08-26[Code Style] Configure code style in the projectsChristian W. Damus4-1/+708
Configure the master settings for Code Style in the org.eclipse.papyrus.infra.core plug-in, including: - Code Formatter - Code Clean-up - Code Templates - Import Sort Order Employ the Oomph Project Configuration tooling to propagate these settings to all other Papyrus main, test, and developer plug-ins, plus the CDO Integration plug-ins. Update the Papyrus Oomph model to remove the workspace-wide code style settings. Change-Id: Id1c7c7fb94c82974a9f1c7cafcfcf32b71ce6c1f
2014-08-25[Code style] Apply clean-up profile to Papyrus Main plug-insCamille Letavernier3-4/+5
2014-08-21[Code style] Apply clean-up and formatter on Main plug-insCamille Letavernier12-271/+279
2014-08-20[Releng] Update Papyrus version to 1.0.1 in pom.xmlCamille Letavernier1-2/+2
2014-08-20[Releng] Update versions to 1.0.1Camille Letavernier2-6/+6
2014-07-24437217: [Editors] In-place reloading of model resources in the editorsChristian W. Damus2-29/+31
https://bugs.eclipse.org/bugs/show_bug.cgi?id=437217 In situ editor reloading. Introduces an IReloadableEditor adapter protocol with an implementation in the CoreMultiDiagramEditor that implements internal destruction of the ServicesRegistry and nested editors. Some refactoring of the initialization and disposal code in the editor class hierarchy and dependencies facilitates reuse of init/dispose code in the reload scenario. The re-loading of an editor is deferred until it is next activated, unless it is already the active editor (can happen when "Save All" is invoked). Editor re-load notifications to dependent views like Model Explorer and Outline. A new listener protocol informs dependents before and after reload so that they may properly dispose of obsolete state and re-initialize when the editor is reloaded. Also ensure that an editor is only reloaded once when some resource that it depends on has changed, not once for each resource. State restoration tokens. Re-load listeners can insert tokens into the re-load event that capture state to be restored after the re-load. Listeners retrieve and apply these tokens after the editor re-loads itself. Current state restoration includes: - tree node expansion and selection state in the Model Explorer view - diagram outline view: which presentation (tree or overview thumbnail) is active - which workbench part is active, such that the correct selection is reflected in views such as Model Explorer, Outline, and Properties - current active diagram in the re-loaded editor - edit-part selections in all diagrams - selection (columns and rows, not individual cells) in table editors - palettes in each diagram (or palette pages when the Palette View is open): * active tool * pinnable stack tool selection * drawer expansion state * drawer scroll position The Palette View support incidentally fixes loss of palette state when switching between Papyrus editors, caused by the PapyrusPaletteSynchronizer. JUnit regression tests for various aspects of editor re-load. Includes a fix for an NPE in the Validation View's content provider that occurs in several tests when an editor is closed or re-loaded. Also support for tests that need to load more than one test-fixture model and/or open more than one editor. Change-Id: Ic0f654ab138d3e091f81f1e9159bcca80d6bb0a5
2014-06-04[Releng] Remove the (Incubation) suffix from all (main) plug-ins andCamille Letavernier2-2/+2
features Update the Bundle test accordingly
2014-05-13[433192] - Explicit synchronization between active inner IEditorPage inmgolubev2-4/+130
multi-editor and PaletteView Change-Id: I88d9e13b0347ae809b836766040e6ee458d2a7b7 Signed-off-by: mgolubev <golubev@montages.com>
2014-04-17[releng] Generated all the pom.xml files for the plugins and featuresLaurent Wouters1-0/+14
Command: python releng/toolkit/tycho-genertor.py Signed-off-by: Laurent Wouters <laurent.wouters@cea.fr>
2014-03-14[Releng] Fix dependency versionsCamille Letavernier2-5/+5
2013-11-13263430: [General] Add relengCamille Letavernier2-6/+6
https://bugs.eclipse.org/bugs/show_bug.cgi?id=263430 Luna: Update plug-in version numbers to 1.0.0
2013-07-04[Releng] Update Papyrus version to 0.10.1cletavernie2-6/+6
2013-02-21398712: [Core] Multiple issues with the PageManagercletavernie1-0/+4
https://bugs.eclipse.org/bugs/show_bug.cgi?id=398712 401434: [Core] The CoreEditor shall be covered with integration tests https://bugs.eclipse.org/bugs/show_bug.cgi?id=401434 Missing classes from previous commits
2012-11-23391945: [Refactoring] Part 2: Refactoring on Kepler (0.10)cletavernie3-30/+53
https://bugs.eclipse.org/bugs/show_bug.cgi?id=391945
2012-09-18Kepler: Update plug-in versions to 0.10.0cletavernie2-7/+9
2012-09-17380517: [Papyrus] We should use explicit plug-in dependencies whenever possiblecletavernie2-7/+3
https://bugs.eclipse.org/bugs/show_bug.cgi?id=380517 + removed some unused dependencies and imports
2012-06-12344017: [General] Papyrus uses internal methods that don't exist in Eclipse 4.1rschnekenbu1-1/+2
https://bugs.eclipse.org/bugs/show_bug.cgi?id=344017 - removing specific perspective listener on startup as this can only lead to bogus behavior. No action is made by this listener currently, so removing it should not be noticeable.
2012-03-22357348: [Build] Papyrus shall provide a source buildcletavernie3-4/+9
https://bugs.eclipse.org/bugs/show_bug.cgi?id=357348 Fixed illformed build.properties files
2012-02-16344017: [General] Papyrus uses internal methods that don't exist in Eclipse 4.1ptessier2-159/+216
https://bugs.eclipse.org/bugs/show_bug.cgi?id=344017
2011-12-09365919: [Architecture - SVN - Build] Rewrite the Buildcletavernie1-1/+4
https://bugs.eclipse.org/bugs/show_bug.cgi?id=365919 Removed some reexported dependencies.
2011-11-09362162: [Architecture - Refactoring] The plug-ins should be renamed to match ↵cletavernie13-24/+23
their layer's qualified name https://bugs.eclipse.org/bugs/show_bug.cgi?id=362162
2011-11-04362162: [Architecture - Refactoring] The plug-ins should be renamed to match ↵cletavernie1-1/+1
their layer's qualified name https://bugs.eclipse.org/bugs/show_bug.cgi?id=362162
2011-11-04362162: [Architecture - Refactoring] The plug-ins should be renamed to match ↵cletavernie4-7/+8
their layer's qualified name https://bugs.eclipse.org/bugs/show_bug.cgi?id=362162
2011-10-27359057: [Architecture - SVN - Build] The Papyrus architecture should be ↵cletavernie2-25/+29
refactored https://bugs.eclipse.org/bugs/show_bug.cgi?id=359057 Update the plug-in versions and dependencies over Papyrus plug-ins to 0.9.0
2011-10-25359057: [Architecture - SVN - Build] The Papyrus architecture should be ↵cletavernie15-0/+1177
refactored https://bugs.eclipse.org/bugs/show_bug.cgi?id=359057
2011-10-25359057: [Architecture - SVN - Build] The Papyrus architecture should be ↵cletavernie13-0/+456
refactored https://bugs.eclipse.org/bugs/show_bug.cgi?id=359057

    Back to the top