... | ... | @@ -114,10 +114,9 @@ If needed: Adding a repository containing “unofficial” plugins to the AF3 re |
|
|
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 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!)
|
|
|
1. 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))
|
|
|
2. Add the plugin to the list of plugins in `org.fortiss.af3.phoenix.feature/feature.xml` (keep lexicographic order!)
|
|
|
3. 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
|
|
|
--------------------------------
|
... | ... | @@ -130,15 +129,15 @@ Update Oomph installation script |
|
|
5. Commit & push the result.
|
|
|
6. Create a MR to master at [https://git.fortiss.org/af3/fortiss-std-env](https://git.fortiss.org/af3/fortiss-std-env) (the merge should not be executed until the actual plugin is merged in the af3 and/or kernel repos!)
|
|
|
|
|
|
Adjust the Maven build process to consider the added plugins
|
|
|
------------------------------------------------------------
|
|
|
|
|
|
1. Perform a local installation for local AF3 RCP builds as described in the [Local Build](Setting_up_a_local_build) documentation.
|
|
|
2. After a successful local build of the AF3 RCP, follow the steps described in [Adding plugins / modifying the plugin list](Setting_up_a_local_build).
|
|
|
|
|
|
Adjust the Run Configurations to consider the added plugins
|
|
|
------------------------------------------------------------
|
|
|
1. Create a new branch for https://git.fortiss.org/af3/af3-products (according to your issue number).
|
|
|
2. Add there in all three config files (win64.launch, linux64.launch, mac64.launch) your new plugins after the "selected_workspace_bundles" key similar to the already existing plugins (like `<setEntry value="org.fortiss.tooling.base@default:default"/>`).
|
|
|
3. Commit & push the result.
|
|
|
4. Create a MR to master at https://git.fortiss.org/af3/af3-products |
|
|
\ No newline at end of file |
|
|
4. Create a MR to master at [https://git.fortiss.org/af3/af3-products](https://git.fortiss.org/af3/af3-products) (the merge should not be executed until the actual plugin is merged in the af3 and/or kernel repos!)
|
|
|
|
|
|
Adjust the Maven build process to consider the added plugins
|
|
|
------------------------------------------------------------
|
|
|
|
|
|
1. Perform a local installation for local AF3 RCP builds as described in the [Local Build](Setting_up_a_local_build) documentation.
|
|
|
2. After a successful local build of the AF3 RCP, follow the steps described in [Adding plugins / modifying the plugin list](Setting_up_a_local_build). |
|
|
\ No newline at end of file |