... | ... | @@ -141,4 +141,5 @@ Adjust the Maven build process to consider the added plugins |
|
|
|
|
|
1. Install an AF3 developer installation for local building as described in the [local build documentation](https://git.fortiss.org/af3/af3/-/wikis/Setting_up_a_local_build#local-build). This will enable you to perform a Maven Build to get in the end a local AF3 build. However, do not execute yet the Maven Build (skip the third step ["triggering a maven build"](https://git.fortiss.org/af3/af3/-/wikis/Setting_up_a_local_build#triggering-a-maven-build)), because you need to adjust some parts of the Maven Build for your new plugin(s): see next step.
|
|
|
2. Follow the steps described in ['Adjust your build'](https://git.fortiss.org/af3/af3/-/wikis/Setting_up_a_local_build#adjust-your-build) (not everything there might be needed, but the adjustment of the POM file is definitely something that needs to be done).
|
|
|
3. You should now check if you could build with all your changes/adjustments a local AF3 build. For that go back to the [local build documentation](https://git.fortiss.org/af3/af3/-/wikis/Setting_up_a_local_build#local-build) and execute the previously skipped third step of ["triggering a maven build"](https://git.fortiss.org/af3/af3/-/wikis/Setting_up_a_local_build#triggering-a-maven-build). If it can be build successfully, you should be ready to merge all your changes. |
|
|
\ No newline at end of file |
|
|
3. You should now check if you could build with all your changes/adjustments a local AF3 build. For that go back to the [local build documentation](https://git.fortiss.org/af3/af3/-/wikis/Setting_up_a_local_build#local-build) and execute the previously skipped third step of ["triggering a maven build"](https://git.fortiss.org/af3/af3/-/wikis/Setting_up_a_local_build#triggering-a-maven-build). If it can be build successfully, you should be ready to merge all your changes.
|
|
|
4. Merge your branches for the adjusted build to master. Hereby, it is important to start with the MR for maven-releng to make the pipelines of all other MRs succeed. A reasonable order for merging is for example: `maven-releng -> af3-rcp -> tooling-features -> kernel -> af3-features -> af3 -> af3-tests` (Note, that usually not all of these repositories need to be adjusted for adding a new plugin!) |
|
|
\ No newline at end of file |