Skip to main content
aboutsummaryrefslogtreecommitdiffstats
path: root/plugins/uml/org.eclipse.papyrus.uml.profile/META-INF/MANIFEST.MF
AgeCommit message (Collapse)AuthorFilesLines
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>
2018-04-19Bug 527664 - [AFViewpoints] Architecture Model Editor removeMaged Elaasar1-2/+2
CreationCommandClass property value Converted the Creation/ConversionCommandClass properties in the architecture editor to be of type string instead of Class. They can now reference class names from the workspace (on their project's class path). Also added validation rules for that. Finally, I added a Browse... button in the property sheet to help put values for them. remove some reexport increase version to take in account API tool Change-Id: I6792449fbee70b089f83780c4935242fff72d50b Signed-off-by: Maged Elaasar <melaasar@gmail.com>
2018-01-31Bug 529707 Correct the plugin versions in order to avoid clashing dependenciesQuentin Le Menez1-1/+1
Change-Id: Id1e8a4c1d81c9d7ccd04ca6de352e017eba85cab Signed-off-by: Quentin Le Menez <quentin.lemenez@cea.fr>
2018-01-25Bug 529707 - [Profile] No way to select which ProfileApplicationDelegatePauline DEVILLE1-1/+1
we want to use * Add a Preference Page to select the Profile application delegate to use * Move the External Profile application delegate preference page as sub preference page to the Profile application delegate page Change-Id: I83dfd62742420c158174152c01ed037c83993a95 Signed-off-by: Pauline DEVILLE <pauline.deville@cea.fr>
2018-01-09Bug 515367 - [releng] Uniformization of the end of lines to Unix standardQuentin Le Menez1-38/+38
- Format the EOL of all the files matched by: grep -rIUs . | xargs -Ifile dos2unix -k 'file' Change-Id: I5c41d540a9a67b50de9b912ab35e16cc9a912961 Signed-off-by: Quentin Le Menez <quentin.lemenez@cea.fr>
2017-11-16bug 527195 - [PropertyView][ProfileTab] Create preferences for the label ↵Vincent Lorenzo1-1/+1
displayed in the Applied Stereotype Widget Change-Id: I7a5e20da1b04249ffe49bb38142267bedaee8713 Signed-off-by: Vincent Lorenzo <vincent.lorenzo@cea.fr>
2017-06-12Bug 516250 - [Palette] Actions properties tabs of paletteconfigurationMickael ADAM1-1/+2
file Editor doesn't work https://bugs.eclipse.org/bugs/show_bug.cgi?id=516250 Change-Id: I6754d431b95524af662c049a686ed6f403501831 Signed-off-by: Mickael ADAM <mickael.adam@all4tec.net>
2017-05-05Bug 510951: [Internationalization] Elements from profile does not haveNicolas FAUVERGUE1-1/+2
label displayed https://bugs.eclipse.org/bugs/show_bug.cgi?id=510951 - Manage some missing 'getName()' for the stereotypes - Manage a 'getQualifiedLabel()' for the stereotypes (needed into diagram because of the StereotypeDisplayUtil - Manage differently the get preference of the internationalization: * Use the model set URI to get the correct top URI instead of the resource URI (for profile, the resource was not the correct one needed). - Manage the read-only properties files as 'fake' resources Change-Id: Id303fafdf1a48d9fab2903c20080352f9af02af4 Signed-off-by: Nicolas FAUVERGUE <nicolas.fauvergue@cea.fr>
2017-04-06Bug 514332 - Papyrus should never reexport non-singleton pluginsBenoit Maggi1-0/+1
- remove Required-Bundle Guava (and their re-export) - use package import for Guava dependencies Change-Id: Ie1e383b6b8ed1d57747345c2788c0c63de1f08bb Signed-off-by: Benoit Maggi <benoit.maggi@cea.fr> Signed-off-by: Florian Noyrit <florian.noyrit@cea.fr>
2017-03-30[releng] Update plugins and feature version numbers for Oxygen withFlorian Noyrit1-35/+35
Neon.3 as baseline Change-Id: Icb3b699de6846ce60370a1fedc169e1df741ace2
2016-11-29Bug 496905: [Diagram][ModelExplorer][Table][Dialog] Papyrus must integrateNicolas FAUVERGUE1-1/+2
the internationalization feature provided by UML. https://bugs.eclipse.org/bugs/show_bug.cgi?id=496905 Commit of UML for internationalization. Change-Id: Ia61e5ef4d537f9e9b192bcfe073f921542fe4876 Signed-off-by: Nicolas FAUVERGUE <nicolas.fauvergue@all4tec.net>
2016-09-01Bug 482669 - [Palette] New Palette configuration models shall beMickael ADAM1-1/+2
editable with an advance UI https://bugs.eclipse.org/bugs/show_bug.cgi?id=482669 Patch set 27: - rebase & maj dependency version Patch set 25: - Fix dependency version Patch set 24: - update version to 3.0.0 or 2.1 - take into account of new elemntType version (no more Ids) - refactor ProdileWSModelIndexer to use URI Patch set 23: - rebase - remove CustomElmtTypeFactory Patch set 20: - Fix missing id in manual created advices Patch set 17: - Fix bugs from NiF review patch set 16: - Fix a bug of drag a stereotype then a metaclass => NPE patch set 16: - fix ProfileWorkspaceModelIndex - add shouldIndex(IFile file) to IndexHandler patch set 15: - fix a build.properties Patch set 14: - some minors fixes Patch set 13: - Finalize properties view for actions - implements validators. - Adds plugins to oep.customization.feature Patch set 12: - implement properties view for SetValue Advice, SetStereotype and Runtime advice. - new Explorer dialog(Stereotype, Profile, GenericElement) -... Patch set 11: - final implementation of apply stereotype action properties view - fix feedback from NIF previous review. - fix enable button of generic multipleValueEditor - Styled text for stereotype explorer - add profile explorer - add stereotype attribute explorer - many fixes Patch set 10: - Move created plugin in customization feature Patch set 9: -Fix pom dependencies Patch set 8: - implementation of property view for StereotypesToAplly of Action. - create a Icon Value editor instead of IconDescriptor - Create stereotype selection dialog which display all available stereotype - Create Profile workspace indexer Patch set X: - create StringWithClear Editor - rename property plugin - remove assistant and newChild implementation for palette - use of icon 12*12 from oep.infr.widget Patch set 5: - Fix pom file Patch set 4: - inlude all changes from palette customization branch Patch set 3: - Adds clear filter button for icon explorer. - Adds some newChild management requirement. Patch set 2: - Gets all declared advice kind in add actions. - Adds icon+description to AdviceKindExtensionPoint. - Adds createAdviceBindingConfiguration to AbstractAdviceBindingFactory. - Gets default actions EMF properties view when no View defined in ctx - Manage action buttons enable. Patch set 1: - Adds actions management - Adds properties View for adviceConfiguration - Adds ctrl+clic to create old local palette Conflicts: plugins/uml/properties/org.eclipse.papyrus.uml.properties/META-INF/MANIFEST.MF Change-Id: I1f5caeb9eb411df2886f29ae02d807bb69b79be2 Signed-off-by: Mickael ADAM <mickael.adam@ALL4TEC.net>
2016-08-28Bug 443799 - Fix potential bugs identified by FindBugs in oep.infra.*Florian Noyrit1-5/+5
Bug 499554 - Oxygen release version number moved to 3.0.0. Change-Id: I8e112db7175a5b89eb9b37973639627a6c29e007
2016-03-03Bug 488791: [Tests] Discontinue packaging of tests as fragment bundlesChristian W. Damus1-0/+1
Deprecate the FragmentTestSuiteClass. Convert all test fragments in the Papyrus Main Tests to plug-ins (does require some changes in the tests themselves, especially in the finding of test resources within the bundles and a few cases of making API accessible for testing). Update the aggregate suites accordingly. Change-Id: I91b38b3152fb147d3c4185b00240248344cce95b
2016-03-03Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus1-4/+4
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-48/+32
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-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
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.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-08-21[releng] Neon-1.2.0 modification step by stepQuentin Le Menez1-16/+15
Change-Id: I9126d707fecad85c9b5384b35074deba995b6527 Signed-off-by: Quentin Le Menez <quentin.lemenez@cea.fr>
2014-11-06399859: [Profile Applications] Papyrus shall enable to manage profile ↵Christian W. Damus1-0/+1
applications in separate files https://bugs.eclipse.org/bugs/show_bug.cgi?id=399859 Externalize the UI strings in the control-mode plug-in. (+57 squashed commits) Squashed commits: [31a95fd] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Support basic stereotype repair use cases in decorator model resources. ---- [3eaa4ad] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Improve re-application of externalized profiles for migration scenarios, doing away with hacky internalize and re-externalize steps that make a mess of the ordering of stereotype applications in the resource contents. ---- [fa20519] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Complete the copyright updates. ---- [5af536d] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Pluggable profile-application delegate API makes the private AppliedProfilesProvider redundant. ---- [b1e7f68] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Further copyright updates. ---- [ed0788d] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Now that the required UML2 API is available we can remove work-arounds for access to custom profile- and stereotype-application helpers. ---- [b262c2c] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Fix copyright headers. ---- [c4f04a5] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Support for migration of externally applied profiles to a new version. ---- [1892e18] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Additional slightly less trivial test cases for control-mode refactoring. ---- [7e530bd] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Don't create eCrossReferences() lists that compute and cache derived references that don't need refactoring. ---- [a35a57e] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files The undo of control refactoring for unloaded resources needs the same split treatment as for uncontrol. ---- [83249b2] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Automated tests for control-mode participant for refactoring of decorator models. ---- [d4a5149] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Fixes undo/redo of the uncontrolled refactoring for unloaded decorator models, which when undoing would find that the base uncontrol's undo hadn't yet restored the sub-unit resource in which we need to resolve referenced objects. ---- [46f4998] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Fixes to the automatic saving of decorator-model refactoring in (un)control command: - improve the determination of the editor to save (if any) - ensure that we only try to run the save runnable in the workbench window if on the UI thread ---- [1e65796] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Only prompt the user about save requirement if the control action was UI-initiated. Duh. ---- [75ea465] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Initial support for refactoring of currently loaded and unloaded decorator models that apply profiles directly or indirectly to the packages being controlled. ---- [71dfab4] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Fix errors in Javadocs and allow the control command to re-create a resource that the resource set had attempted to load for proxy resolution but failed because it doesn't exist. ---- [45fe94e] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Packages must also inherit externally applied profiles from their nesting package chain. ---- [24428c1] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Refresh the property sheet for the selected package after externalizing profiles to ensure that the "Applications" tab is showing. ---- [4763809] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Replace "Decorator Model" terminology in the UI with simply "Profile Application". ---- [77c00fb] 399859: [Decorator Models] Papyrus shall enable to manage profile applications in separate files Remember the user's last auto-prompt load selections for initial selection on next open of the same resource. ---- [651fe70] 399859: [Decorator Models] Papyrus shall enable to manage profile applications in separate files Improve JUnit test coverage of core plug-in. ---- [f2d5e7a] 399859: [Decorator Models] Papyrus shall enable to manage profile applications in separate files Add an action in the Decorators property tab for packages to duplicate a loaded or unloaded decorator model with support for filtering out certain profile applications. ---- [37eb425] 399859: [Decorator Models] Papyrus shall enable to manage profile applications in separate files Fix failure to refresh diagram for CSS styles affected by loading a decorator model the first time (and ensure all subsequent, also). ---- [1d62d00] 399859: [Decorator Models] Papyrus shall enable to manage profile applications in separate files Fix problem in refreshing decorator model names in the Decorators property tab. Fix broken "Don't show this again" options in the load-decorator-models wizard. ---- [8ad5bd0] 399859: [Decorator Models] Papyrus shall enable to manage profile applications in separate files Option to suppress prompt to unload conflicting decorator models in the Decorator property tab for packages and instead just automatically unload them (supporting quick switch use case). ---- [dde50a3] 399859: [Decorator Models] Papyrus shall enable to manage profile applications in separate files Do not confuse users by showing the "decorator models available" icon decoration in Model Explorer on models that are decorated by the decorator model that the user opened in the editor. Only show the icon for referenced ("library") models that are reachable from such models. ---- [a82eb1b] 399859: [Decorator Models] Papyrus shall enable to manage profile applications in separate files Improve liveness of action enablement and other tasks (esp. on the UI thread) that depend on the decorator model index. Implement a general-purpose Jobs-based ListenableFuture to support reporting blocked UI tasks in the blocked-jobs dialog. A few more rename refactorings in the API. Improve JUnit test coverage (and fix problems found by new tests). ---- [1cdaa01] 399859: [Decorator Models] Papyrus shall enable to manage profile applications in separate files Implement Decorators property tab for packages that have decorator models, to provide easy access to loading and unloading them. ---- [de1cc1c] 399859: [Decorator Models] Papyrus shall enable to manage profile applications in separate files Rationalize the handling of empty decorator models by prompting to delete and deleting all Papyrus model member resources in case of deletion. ---- [9bb18ac] 399859: [Decorator Models] Papyrus shall enable to manage profile applications in separate files Never prompt to load additional decorator models when opening a decorator model, even if the user model that it decorates has more decorators available and the preference to auto-prompt is enabled. ---- [b1e3315] 399859: [Decorator Models] Papyrus shall enable to manage profile applications in separate files Promote the Workspace Model Index and any-root-namespace content type describer APIs to the infra layer. ---- [f708155] 399859: [Decorator Models] Papyrus shall enable to manage profile applications in separate files Ensure responsiveness of label decorators. Apply label decorations to workspace resources in Project Explorer that are decorator models. ---- [4379197] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files WORKAROUNDS for absence of the required new UML API until it becomes available. ---- [68db5f0] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files WORKAROUNDS for absence of the required new UML API until it becomes available. ---- [0bf4163] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Add missing dependency information to top POMs. ---- [04d0935] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Add new plug-ins to top POMs. ---- [d4346cf] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Releng integration. ---- [40cfc0d] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Fix further refresh issues in diagrams when loading decorator models. When existing stereotype applications are loaded, they won't emit SET notifications for the base_Xyz references. Instead, they eventually emit RESOLVE notifications when their base reference proxies are resolved. ---- [f393d19] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Further API refactorings for 'decorator model' terminology. ---- [a3e9dd4] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Only prompt to load decorator models if opening in an editor. ---- [38885bc] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Refactor for 'decorator model' terminology and move the plug-ins into the main source tree. ---- [63c305e] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Various usability enhancements: - label decorators in Model Explorer and applied profiles in package properties indicating source profile externalization model names - prevent conflicts in externalization of profile applications into existing resources - never present profile application resources as available that conflict with native profile applications - revert ModelSet save change that breaks initialization of model from existing UML resource ---- [c1bb42b] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Profile application externalization wizard enhancements: - remember last file extension entered by the user (in case more than just .uml) - let user specify the model name, when creating a new file - verify that when adding to an existing file, it's a profile application model - include the profile application model name in the index ---- [4d1169b] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Enforce uniqueness of profile applications: prevent loading of multiple external profile applications that apply the same profile to the same package. ---- [ac15898] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Require saving dirty profile-application resources before unloading them. ---- [9ad9b0f] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Ensure that PapyrusListeners see changes in profile-application resources as well as the user-model resources. Fix the PapyrusStereotypeListener to handle unloading of a resource containing stereotype applications to interpret the stereotypes as being unapplied. ---- [4c52edd] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Handle problems in (re)building the workspace model index, add a listener protocol, and make it independent of the UML layer. ---- [402c77c] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Add a label decorator (just a placeholder icon for now) for models that have available unloaded profile applications. Add a preference (enabled by default) to prompt to load available profile applications on opening a model, if it has unloaded profile applications available. ---- [8566806] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Add some JUnit tests for the workspace model index framework. ---- [6f500b8] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Ensure that the user models to which a profile-application model contributes profile applications are loaded when the latter is loaded in the Papyrus Editor. ---- [16a0884] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Enable storage of profile applications in UML resources anywhere in the workspace, even in different projects than the models to which they are applied. Uses a new workspace-wide index of cross references between profile-application resources and user model resources, built at start-up and maintained in the background as the workspace changes. ---- [6fe515d] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Hide profile application models in the Model Explorer by default. ---- [69ef817] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Added context-menu actions in the Model Explorer for loading available profile applications that are not yet loaded and for unloading and loaded externalized profile applications (for any currently open controlled units). ---- [d9bb954] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Initial implementation of separate storage of profile applications and their defined stereotype applications in a separate resource. Includes - externalize profile applications refactoring wizard - internalize profile applications refactoring wizard - load profile applications context-menu action in Project Explorer - unload profile applications context-menu action in Model Explorer - enhanced Profile applications table in Properties view for packages ---- [b8578c3] 399859: [Profiles] Papyrus shall enable to manage profile applications in separate files Propagate standard JDT preferences to the sandbox projects. Signed-off-by: Christian W. Damus <give.a.damus@gmail.com> ---- [ec61dd2] 399859: [Profile Applications] Papyrus shall enable to manage profile applications in separate files Update build dependencies to pick up latest UML2 integration build with new APIs required for profile applications feature. Change-Id: Ifa20519ec3209393c88e0a1ac322eac715e541f4
2014-09-15[Releng] Change plug-ins version to 1.1.0Camille Letavernier1-15/+15
2014-08-20[Releng] Update versions to 1.0.1Camille Letavernier1-46/+46
2014-07-30435995: Profile version numbers missing in the profile-upgrade-popupGabriel Pascual1-46/+46
message https://bugs.eclipse.org/bugs/show_bug.cgi?id=435995 Patch #1 : - Add colums for display version in refresh dialog - Move Papyrus profile definition - Add implementation of previous version column filling in label provider Patch #2 : - Put ProfileApplication as context for Refresh Dialog (Label Provider and Content provider) - Enforce save of version in ApplyProfileCommand Patch #3 : - Fix API compatibility - Fix providers of ProfileApplication Change-Id: If83ee0dee94ce88f38e8e47a04460f74add42b21 Signed-off-by: Gabriel Pascual <gabriel.pascual@all4tec.net>
2014-05-09434302: Stereotype repair problems with nested profiles and non-root ↵Christian W. Damus1-1/+2
applications https://bugs.eclipse.org/bugs/show_bug.cgi?id=434302 Ensure that the Reapply Profiles Service doesn't run its check for out-of-date profiles until after an initial stereotype repair operation (if any) has completed. Stereotype repair may end up reapplying the profiles that were out of date, but in any case, it is important to perform repair operations before optional profile migration.
2014-03-14[Releng] Fix dependency versionsCamille Letavernier1-17/+17
2014-03-14399860: Papyrus shall enable to customize the creation policy of viewsLaurent Wouters1-1/+2
https://bugs.eclipse.org/bugs/show_bug.cgi?id=399860 Signed-off-by: Laurent Wouters <laurent.wouters@cea.fr>
2014-02-14386118: [EMF Facet] Papyrus should progressively support EMF Facet 0.2ptessier1-2/+1
https://bugs.eclipse.org/bugs/show_bug.cgi?id=386118
2014-02-10386118: [EMF Facet] Papyrus should progressively support EMF Facet 0.2Patrick tessier1-1/+3
https://bugs.eclipse.org/bugs/show_bug.cgi?id=386118 import EMF-FACET
2014-01-16422745: Linkage error, if guava 13 is availableCamille Letavernier1-1/+1
https://bugs.eclipse.org/bugs/show_bug.cgi?id=422745 Tentative to fix the Guava Linkage error issues. Papyrus now depends on Guava >= 11.0.0 - Removed usages of deprecated APIs - Increased minimum version dependency to Guava 11 to allow usage of new APIs
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-11/+11
2013-05-30404282: Simple Profile Creation/Validation Errorscletavernie1-0/+1
https://bugs.eclipse.org/bugs/show_bug.cgi?id=404282
2013-05-21407686: [General] Inconsistent Guava importsrschnekenbu1-1/+1
https://bugs.eclipse.org/bugs/show_bug.cgi?id=407686 - updating all com.google.guava* imports to com.google.guava:bundle-version="10.0.1" in Manifest.MF - updating some preferences files where date was stored and is not stored anymore.
2013-05-14382733: [validation] Papyrus shall to compute constraints from the profile ↵ptessier1-1/+1
at the model level https://bugs.eclipse.org/bugs/show_bug.cgi?id=382733
2013-03-15396735: [Read only] corrupted model because of half saved modelmvelten1-1/+2
https://bugs.eclipse.org/bugs/show_bug.cgi?id=396735 397762: [ReadOnly] Unable to override a IReadOnlyHandler once register https://bugs.eclipse.org/bugs/show_bug.cgi?id=397762 397758: [PapyrusCore] ModelSet should be more extensible https://bugs.eclipse.org/bugs/show_bug.cgi?id=397758
2012-10-26392438: [Core Services] Papyrus should provide a LabelProvider servicecletavernie1-1/+2
https://bugs.eclipse.org/bugs/show_bug.cgi?id=392438 LabelProviderService is now partially used.
2012-10-15391945: [Refactoring] Part 2: Refactoring on Kepler (0.10)cletavernie1-2/+2
https://bugs.eclipse.org/bugs/show_bug.cgi?id=391945
2012-09-18Kepler: Update plug-in versions to 0.10.0cletavernie1-10/+10
2012-09-17380517: [Papyrus] We should use explicit plug-in dependencies whenever possiblecletavernie1-6/+11
https://bugs.eclipse.org/bugs/show_bug.cgi?id=380517 + removed some unused dependencies and imports
2012-08-02386492: [Libraries - Profiles] All Libraries and Profiles should be loaded ↵cletavernie1-0/+1
in read-only mode https://bugs.eclipse.org/bugs/show_bug.cgi?id=386492
2012-07-31330349: [All diagrams]Applying a profile with a Property of an undefined ↵ptessier1-1/+2
Type corrupts the model and makes save action crash https://bugs.eclipse.org/bugs/show_bug.cgi?id=330349
2012-06-29269494: Manage application of stereotype properties as other element in the ↵cletavernie1-0/+1
diagram https://bugs.eclipse.org/bugs/show_bug.cgi?id=269494 Improve the label of the AppliedStereotypeProperty in the properties view
2012-06-22370816: [All diagrams] Profiles should be automatically refreshedcletavernie1-1/+3
https://bugs.eclipse.org/bugs/show_bug.cgi?id=370816
2012-02-14371460: [UML Diagram Common] The UML Diagram Common plug-in should be splitcletavernie1-11/+5
https://bugs.eclipse.org/bugs/show_bug.cgi?id=371460
2012-01-19330176: [All Diagrams] Papyrus shall enable to display stereotype properties ↵ptessier1-2/+3
in a dedicated compartment. https://bugs.eclipse.org/bugs/show_bug.cgi?id=330176
2012-01-13269494: Edit properties of an applied stereotypes.ptessier1-0/+1
https://bugs.eclipse.org/bugs/show_bug.cgi?id=269494
2011-11-10362162: [Architecture - Refactoring] The plug-ins should be renamed to match ↵cletavernie1-19/+19
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-3/+3
their layer's qualified name https://bugs.eclipse.org/bugs/show_bug.cgi?id=362162
2011-11-03362162: [Architecture - Refactoring] The plug-ins should be renamed to match ↵cletavernie1-0/+34
their layer's qualified name https://bugs.eclipse.org/bugs/show_bug.cgi?id=362162
2011-11-03362162: [Architecture - Refactoring] The plug-ins should be renamed to match ↵cletavernie1-11/+0
their layer's qualified name https://bugs.eclipse.org/bugs/show_bug.cgi?id=362162

Back to the top