Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat (limited to 'plugins/doc/org.eclipse.papyrus.developer.doc/resource/guidelines.mediawiki')
-rw-r--r--plugins/doc/org.eclipse.papyrus.developer.doc/resource/guidelines.mediawiki35
1 files changed, 20 insertions, 15 deletions
diff --git a/plugins/doc/org.eclipse.papyrus.developer.doc/resource/guidelines.mediawiki b/plugins/doc/org.eclipse.papyrus.developer.doc/resource/guidelines.mediawiki
index a372961c615..89dfecdbd46 100644
--- a/plugins/doc/org.eclipse.papyrus.developer.doc/resource/guidelines.mediawiki
+++ b/plugins/doc/org.eclipse.papyrus.developer.doc/resource/guidelines.mediawiki
@@ -334,7 +334,7 @@ These rules apply to all plug-ins and features developed for the Papyrus Eclipse
==== Plug-ins ====
-*All plug-ins must compile and run with Java 11 (''Execution Environment = JavaSE-11'') since 2020-12.
+*All plug-ins must compile and run with Java 17 (''Execution Environment = JavaSE-17'') since 2023-06.
*Plug-in provider : ''Eclipse Modeling Project''
*Version :
**Juno : ''0.9.2.qualifier''
@@ -482,8 +482,8 @@ This list contains all points that should be verified before committing the plug
*Plugin id should correspond to Papyrus standards. It should be meaningfull and distinguishable from other plugins (to avoid having plugins org.eclipse.papyrus.editors and org.eclipse.papyrus.editor)
**Plugin id and project name should be exactly the same, to ease the process build
*Plugin should be compatible with the java 11 library:
-**Minimal execution environment is JavaSE-11
-**JRE system library should be specified to JavaSE-11
+**Minimal execution environment is JavaSE-17
+**JRE system library should be specified to JavaSE-17
*Plugin should contain the 'about.html' file at the root of the plugin
**Check also that this file is included in the source and binary builds (build.properties -> binary build, source build)
*Plugin should be internationalized, with plugin.properties file or with the new system: PDE Tools > Internationalize
@@ -1495,22 +1495,25 @@ Papyrus editor add some new features to GMF, and needs specific generation. Here
=== How to generate a diagram for Papyrus ===
==== Prerequisites ====
-
-Install following Eclipse environment:
-* GMF tooling see version http://download.eclipse.org/modeling/gmp/gmf-tooling/updates/releases-3.3.1a
-* the xtend2 extensions of GMF tooling.
-* xtend editor (to manage file encoding problem) http://download.eclipse.org/modeling/tmf/xtext/updates/composite/releases/
-
-It is recommended to run the generation in a second Eclipse Application launched from your running Eclipse instance.
-Add the following developer plugins to your workspace (first instance).
-
-* org.eclipse.papyrus.gmfgenextension
-* org.eclipse.papyrus.codegen
-* org.eclipse.papyrus.def
+From the Papyrus update site, you need to install the Papyrus Diagram Generation Tools feature.
+[[Image:images/PapyrusDiagramGenInstallation.png]]
+
+If you want to work with the generation plug-ins in your workspace, add the following developer plugins to your workspace (first instance).
+
+* org.eclipse.papyrus.codegen
+* org.eclipse.papyrus.dev.assistants.codegen
+* org.eclipse.papyrus.gmf.codegen
+* org.eclipse.papyrus.gmf.codegen.edit
+* org.eclipse.papyrus.gmf.codegen.ui
+* org.eclipse.papyrus.gmf.codegen.xtend
+* org.eclipse.papyrus.gmf.codegen.xtend.ui
+* org.eclipse.papyrus.gmf.common
+* org.eclipse.papyrus.gmf.validate
* org.eclipse.papyrus.dev.assistants.codegen (optional, needed in case of generating a diagram assistant, as shown below)
Now use the "debug/run configurations" dialog to create a new Eclipse Application instance and launch it.
+
==== Setup your runtime application ====
This step is executed in the 2nd Eclipse instance that includes executable versions of the three Papyrus developer plugins that have been added to the workspace of the first instance (see preceding step).
@@ -1590,6 +1593,8 @@ where '''getyourTemplateNameEmitter()''' : is the new TextEmitter defined
You just now have to run your transformation as explained before in this page. Be careful to refresh your projects in your runtime application if you generate in this mode.
=== Papyrus Extension Root Node Description ===
+Since Papyrus for Eclipse 2021-09, the Papyrus Extension doesn't exist anymore, but its concepts have been included directly in the GMF metamodel. So this documentation is half-deprecated.
+
==== Compartment Visibility Preference ====
Description : This extension allows to define the default visibility for the compartments. The compartments not referenced by this node are visible by default.

Back to the top