Skip to main content
aboutsummaryrefslogtreecommitdiffstats
path: root/plugins/infra/org.eclipse.papyrus.infra.extendedtypes.emf
AgeCommit message (Collapse)AuthorFilesLines
2016-02-12Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus92-6902/+0
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 architecture (& builds) ↵Christian W. Damus7-9/+9
for Papyrus https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220 Refactor the Properties Model bundles into the Infra Layer. The *.views.properties.model[.edit,.editor] bundles are renamed as *.infra.properties[.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 *.views.properties.model* bundles, because otherwise the clash of EMF model registrations would cause run-time errors. The *.views.properties.environment extension point is moved to *.infra.properties.environments. The *.views.properties.context extension point has the <context> element moved to a new *.infra.properties.contexts 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. Damus6-225/+5
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220 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 infra.services.edit bundle to a new infra.services.edit.ui 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-06Bug 485220: Removing unused bundle dependencies in Infra layerChristian W. Damus1-4/+1
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220
2016-01-06Bug 485220: Remove some unused dependencies in infra layerChristian W. Damus1-2/+0
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220 Simple removal of dependencies declared in the manifests of infra layer bundles that aren't used by those bundles. Some of these dependencies are invalid (UI dependencies in core bundles, misplaced UML or GMF/GEF dependencies, etc.) that confuse the architectural analysis.
2015-08-21[releng] Neon-1.2.0 modification step by stepQuentin Le Menez2-15/+12
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-02-11Bug 459566: [Releng] Consider letting Tycho use JDT's project settings for ↵Christian W. Damus3-9/+12
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 Letavernier1-8/+8
2014-08-26[Code Style] Configure code style in the projectsChristian W. Damus2-0/+356
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 Letavernier37-394/+346
2014-08-21[Code style] Apply clean-up and formatter on Main plug-insCamille Letavernier50-632/+1103
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 Letavernier1-8/+8
2014-06-04[Releng] Remove the (Incubation) suffix from all (main) plug-ins andCamille Letavernier1-1/+1
features Update the Bundle test accordingly
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 Letavernier1-10/+10
2014-03-07Bug 386118 - [EMF Facet] Papyrus should progressively support EMF Facetptessier1-0/+12
0.2 add comment and custom have been maigrated
2014-02-16Merge branch 'master' into committers/rschnekenbu/master/extendedtypesrschnekenbu1-1/+0
Conflicts: plugins/sysml/diagram/org.eclipse.papyrus.sysml.diagram.common/META-INF/MANIFEST.MF
2014-02-16Bug 399858 - [Documentation] Papyrus shall have an embeddedrschnekenbu101-1758/+4172
documentation https://bugs.eclipse.org/bugs/show_bug.cgi?id=399858 - Migration to Luna
2013-11-13263430: [General] Add relengCamille Letavernier1-11/+11
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.1cletavernie1-6/+6
2012-09-18Kepler: Update plug-in versions to 0.10.0cletavernie1-8/+10
2012-09-17380517: [Papyrus] We should use explicit plug-in dependencies whenever possiblecletavernie1-5/+7
https://bugs.eclipse.org/bugs/show_bug.cgi?id=380517 + removed some unused dependencies and imports
2012-03-22357348: [Build] Papyrus shall provide a source buildcletavernie1-2/+1
https://bugs.eclipse.org/bugs/show_bug.cgi?id=357348 Fixed illformed build.properties files
2012-03-21365919: [Architecture - SVN - Build] Rewrite the Buildcletavernie2-3/+4
https://bugs.eclipse.org/bugs/show_bug.cgi?id=365919
2011-11-09362162: [Architecture - Refactoring] The plug-ins should be renamed to match ↵cletavernie30-233/+233
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 ↵cletavernie3-10/+11
their layer's qualified name https://bugs.eclipse.org/bugs/show_bug.cgi?id=362162
2011-11-02362162: [Architecture - Refactoring] The plug-ins should be renamed to match ↵cletavernie37-0/+3904
their layer's qualified name https://bugs.eclipse.org/bugs/show_bug.cgi?id=362162

    Back to the top