Skip to main content
aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2019-11-26Bug 553107: [Xtext] The Xtext editors must allows to display line numberVincent Lorenzo1-1/+1
Change-Id: Ib838da56780b6c6fbc66be4ce296cbadc429c442 Signed-off-by: Vincent Lorenzo <vincent.lorenzo@cea.fr>
2018-09-05Bug 536594: [Properties][OpaqueExpression][XText] the change of theVincent Lorenzo1-3/+3
language to use doesn't work propertly with Xtext editor Change-Id: I05065a52f8182da46190d5d4c36d891c57e461fb Signed-off-by: Vincent Lorenzo <vincent.lorenzo@cea.fr> Signed-off-by: Nicolas FAUVERGUE <nicolas.fauvergue@cea.fr>
2018-06-29Bug 536425: [Xtext] All Papyrus Xtext plugins must be regeneratedNicolas FAUVERGUE1-1/+1
Change-Id: I5855fe718bec8ae29f58dafe1a8a8f57860c97ec Signed-off-by: Nicolas FAUVERGUE <nicolas.fauvergue@cea.fr>
2018-05-28Bug 535185 - Add Automatic-Module-Name header for Java 9 compatibilityBenoit Maggi1-0/+1
- add Automatic-Module-Name with the same value as Bundle-SymbolicName in all Manifest.MF - quality fix : remove unused import Change-Id: Icd3e4376bc9e61e360ac61522b967a088a248480 Signed-off-by: Benoit Maggi <benoit.maggi@cea.fr>
2017-12-14Bug 527876 - [Property View] Facilitate the use of xtext editors in property ↵Ansgar Radermacher1-0/+4
view - Export elements of oep.uml.properties.xtext plugin - Add missing copyright messages in some classes of the oep.uml.properties.xtext plugin - Add "getter" method for accessing the text-control in XtextLanguageEditor - Add new abstract class that specific xtext-editors should subclass. - Provide the editing of state-machine transitions via xtext as an example. - Add LANGUAGE string constant to TransitionEditorConfigurationContribution Signed-off-by: Ansgar Radermacher <ansgar.radermacher@cea.fr> Change-Id: Ied704ae35277d324595ee8e3b874206bbb989313
2017-08-29Bug 520271 - [Property View] Generator should ignore redefined properties.Vincent Lorenzo1-1/+1
Change-Id: I5d73f2441ff5e23f937ab155488cf29fb249a65c Signed-off-by: Vincent Lorenzo <vincent.lorenzo@cea.fr>
2016-08-28Bug 443799 - Fix potential bugs identified by FindBugs in oep.infra.*Florian Noyrit1-2/+2
Bug 499554 - Oxygen release version number moved to 3.0.0. Change-Id: I8e112db7175a5b89eb9b37973639627a6c29e007
2016-08-08Bug 498754: [Table] NattablePropertyEditor and TreeTablePropertyEditorNicolas FAUVERGUE1-1/+1
have dependency on Notation#View -> it must be removed https://bugs.eclipse.org/bugs/show_bug.cgi?id=498754 - Remove View from TreeNattablePropertyEditor - Some deprecated in NattablePropertyEditor (not removed to manage API compatibility) Change-Id: I9ccb0ee315c9d3252aa4f3ada0d86a44bd2c37af Signed-off-by: Nicolas FAUVERGUE <nicolas.fauvergue@all4tec.net>
2016-08-04Bug 492891: [Table] Link with editor: different behavior of diagrams andNicolas FAUVERGUE1-1/+1
tables https://bugs.eclipse.org/bugs/show_bug.cgi?id=492891 - The owner of table can be modified and the context can't be modified - Add the 'Table', 'Appearance' and 'Paste' tab in properties view when an the table is the current editor This looks to correct other bugs: - Bug 492605 - [Table][Properties][usability] error message "Properties are not available" - Bug 492615 - [Table][usability] inconsistency of properties view N.B: The 'invert axis' button doesn't work correctly, but another gerrit manage it Change-Id: I9d22713e81bf865bc59fbd10a34b270e75aa5037 Signed-off-by: Nicolas FAUVERGUE <nicolas.fauvergue@all4tec.net>
2016-08-04Bug 499002: [Property][Table] Table context updated with View instead ofNicolas FAUVERGUE1-1/+1
semantic element https://bugs.eclipse.org/bugs/show_bug.cgi?id=499002 Modify the object to get the correct table context: - Element of View for NattablePropertyEditor - View for StereotypeDisplayNattablePropertyEditor Change-Id: I9cbcf849f1f439be130cfb82577377761d16f9b8 Signed-off-by: Nicolas FAUVERGUE <nicolas.fauvergue@all4tec.net>
2016-03-03Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus1-1/+1
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. Damus1-21/+3
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-12Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus1-30/+30
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/+2
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220 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
2015-08-21[releng] Neon-1.2.0 modification step by stepQuentin Le Menez1-30/+29
Change-Id: I9126d707fecad85c9b5384b35074deba995b6527 Signed-off-by: Quentin Le Menez <quentin.lemenez@cea.fr>
2015-04-08Bug 463881: [XText] The ValueSpecification XText editor in propertiesNicolas FAUVERGUE1-1/+3
view must be defined by XWT element https://bugs.eclipse.org/bugs/show_bug.cgi?id=463881 - Recvery code which allow to get the direct editor configuration to get it from XWT attribute with java reflexive instead of getting direct editor configuration from object to edit with defined extension points Change-Id: I1aa730f216873ea0912bd705ea63761d7e2c69a5 Signed-off-by: Nicolas FAUVERGUE <nicolas.fauvergue@all4tec.net> Reviewed-on: https://git.eclipse.org/r/45231 Reviewed-by: vincent lorenzo <vincent.lorenzo@cea.fr> Tested-by: vincent lorenzo <vincent.lorenzo@cea.fr>
2015-03-30Fix number version for textual editors in papyrusVincent Lorenzo1-1/+3
2015-03-30459747: [XText] Papyrus must provides a XText editor for the ↵Vincent Lorenzo1-27/+26
ValueSpecification + 427136: [Table 2] It should be possible to edit cells representing references using a textual editor Papyrus
2014-09-15[Releng] Change plug-ins version to 1.1.0Camille Letavernier1-8/+8
2014-08-20[Releng] Update versions to 1.0.1Camille Letavernier1-8/+8
2014-03-14[Releng] Fix dependency versionsCamille Letavernier1-1/+2
2014-03-13[Bug 427025] [OCL For Papyrus] Cannot create OCL constraints in LunaAnsgar Radermacher1-1/+3
Show wait cursor before editing starts Re-activate selection of compartment edit part => enable edit on 2nd click Activate context link tool after constraint creation Enable xtext editor in UML tab of property view (currently for OCL only)
2014-03-04Bug 315231 - [All Diagrams] Direct Edit : Xtext / Papyrus integrationAnsgar Radermacher1-0/+1
Xtext editor in property view: only commit, if editor contains changes
2014-03-04323802: [General] Papyrus shall provide a read only modeChristian W. Damus1-1/+2
https://bugs.eclipse.org/bugs/show_bug.cgi?id=323802 Make new Advanced Editing property section sensitive to read-only model elements. Also update the validation infrastructure to account for the new UML2 plug-in structure in Luna (prerequisite for validation of Advanced Editing parsing).
2014-03-04315231: [All Diagrams] Direct Edit : Xtext / Papyrus integrationCamille Letavernier1-1/+1
https://bugs.eclipse.org/bugs/show_bug.cgi?id=315231 - Fix releng
2013-11-13263430: [General] Add relengCamille Letavernier1-20/+22
https://bugs.eclipse.org/bugs/show_bug.cgi?id=263430 Luna: Update plug-in version numbers to 1.0.0
2013-09-06[Bug 315231] Removing dependencies to Xtext fromArnaud Cuccuru1-1/+1
oep.extensionpoints.editors
2013-09-02Bug 315231 - Improvement of xtext integration.acuccuru1-0/+20
Applies patch produced by ITEMIS.

    Back to the top