... | ... | @@ -117,7 +117,7 @@ Register the plugin with the developer product definitions |
|
|
1. Start eclipse.
|
|
|
2. Create a new branch for developer product definition by right-clicking `org.fortiss.af3.phoenix.feature` and following the typical “switch to” procedure. (see [Development Workflow](Development_Workflow))
|
|
|
3. Add the plugin to the list of plugins in `org.fortiss.af3.phoenix.feature/feature.xml` (keep lexicographic order!)
|
|
|
4. Upload the result and create a MR (the merge should not be executed until the actual plugin is merged in the af3 and/or kernel repos!)
|
|
|
4. Upload the result and create a MR at [https://git.fortiss.org/af3/af3-features](https://git.fortiss.org/af3/af3-features) (the merge should not be executed until the actual plugin is merged in the af3 and/or kernel repos!)
|
|
|
|
|
|
Update Oomph installation script
|
|
|
--------------------------------
|
... | ... | @@ -128,7 +128,7 @@ Update Oomph installation script |
|
|
4. Add the plugin to the corresponding plugin set, e.g., “Behaviour”, if it is not yet captured by any of the existing regular
|
|
|
expressions.
|
|
|
5. Commit & push the result.
|
|
|
6. Create a MR to master at https://git.fortiss.org/af3/fortiss-std-env
|
|
|
6. Create a MR to master at [https://git.fortiss.org/af3/fortiss-std-env](https://git.fortiss.org/af3/fortiss-std-env)
|
|
|
|
|
|
Adjust the Maven build process to consider the added plugins
|
|
|
------------------------------------------------------------
|
... | ... | |