... | ... | @@ -34,11 +34,11 @@ For both build, it is needed to have an AF3 developer installation, but with a s |
|
|
```https://git.fortiss.org/af3/fortiss-std-env/-/raw/master/oomph/af3-releng.setup```
|
|
|
. This will install a developer installation ready to build the RCP with maven. You will get the master of "maven-releng" ("org.fortiss.af3.root") as the only repository within this installation.
|
|
|
|
|
|
##### Update to the latest version of the af3 plugins
|
|
|
##### Update to the latest or wanted version of the af3 plugins
|
|
|
When you have your AF3 developer installation with the "maven-releng" repository:
|
|
|
1. Open the view “Git Repositories” from the “Quick access” box in the top-right corner of eclipse.
|
|
|
2. Navigate to “maven-releng > Submodules”.
|
|
|
3. Select all submodules, open the context menu, and select “Switch to > master”
|
|
|
3. Select all submodules, open the context menu, and select “Switch to > master” or switch each submodule separately to the branch you need for your build.
|
|
|
|
|
|
##### Triggering a maven build
|
|
|
When you have your AF3 developer installation with the "maven-releng" repository and the wanted versions of the submodules (e.g., all masters of the plugins, see previous step):
|
... | ... | @@ -75,18 +75,24 @@ Creating a derivate product |
|
|
change in submodules.
|
|
|
|
|
|
##### Adding plugins / modifying the plugin list
|
|
|
- see next explicit section: [Adjust your build](Adjust your build)
|
|
|
|
|
|
- Add additional eclipse plugins as git submodules in the bundles
|
|
|
folder (from a repo `repo-name`)
|
|
|
|
|
|
Adjust your build
|
|
|
---------------------------
|
|
|
|
|
|
Often, you do not want to have/build your current build/product just with the masters of the AF3 plugins, but you want to add your own stuff (based on own branches, submodules, etc.). These are steps you might need (not all are needed for all situations!):
|
|
|
|
|
|
- If you have own/new submodules you want to integrate: Add additional eclipse plugins as git submodules in the bundles folder (from a repo `repo-name`)
|
|
|
- Option 1: In Eclipse's *Git Repositories* view.
|
|
|
- Context menu of *Submodules* -> *Add Submodule...*
|
|
|
- Submodule path: `bundles/<repo-name>`
|
|
|
- Paste clone URL on next wizard page
|
|
|
- Option 2: On the command line: `git submodule add -b <branch> --name "bundles/<repo-name>" https://git.fortiss.org/af3/<repo-name>.git bundles/<repo-name>`
|
|
|
- Create a branch of af3-features and update the git submodule of the
|
|
|
maven-releng repository to point to this branch.
|
|
|
- Add the plugins to the feature definition
|
|
|
- AF3 feature (new branch): `/org.fortiss.af3.root/features/af3/org.fortiss.af3.phoenix.feature/feature.xml`
|
|
|
- If not already done: Add the plugins to the feature definition ([https://git.fortiss.org/af3/af3-features](https://git.fortiss.org/af3/af3-features))
|
|
|
- Modify AF3 feature (create and commit a new branch for this): `/org.fortiss.af3.root/features/af3/org.fortiss.af3.phoenix.feature/feature.xml`, see [here](https://git.fortiss.org/af3/af3/-/wikis/Adding_a_new_plugin#register-the-plugin-with-the-developer-product-definitions)
|
|
|
- Create an additional feature (for more than 1 or 2 plugins).
|
|
|
- Add new features to a separate update site in “releng/” if needed.
|
|
|
- If needed, add new features to a separate update site in “releng/”.
|
|
|
- What is usually always needed is to adjust the POM file:
|
|
|
- Go to your maven build installation (see above: [Local Build]), open in the maven-releng repository the "bundles" folder and adjust the "pom.xml" (create a new branch for this change before committing!). Add your plugins to the others in the same way (a new "<module>" entry for each plugin).
|
|
|
|