... | ... | @@ -16,7 +16,8 @@ by using the Eclipse multi-file search and replace function. |
|
|
found at: [Setting up a local build](Setting_up_a_local_build)
|
|
|
2. Create a release ticket in the issue tracker, and create a matching
|
|
|
branch for each submodule.
|
|
|
3. Select the project `org.fortiss.af3.root` in the Package Explorer
|
|
|
3. Check the plugins and remove for redundant dependencies suing re-export.
|
|
|
4. Select the project `org.fortiss.af3.root` in the Package Explorer
|
|
|
and execute an Eclipse File Search with the following settings
|
|
|
(`Ctrl + H`)
|
|
|
- Containing text = *a.b.c* (Current version number, e.g.,
|
... | ... | @@ -25,26 +26,26 @@ by using the Eclipse multi-file search and replace function. |
|
|
feature.xml, pom.xml, plugin.xml*
|
|
|
- Scope = *Selected resource in ’Package Explorer’*
|
|
|
- No other search option active.
|
|
|
4. You may want to inspect the results of this search before launching
|
|
|
5. You may want to inspect the results of this search before launching
|
|
|
the replace action.
|
|
|
5. If the changes are fine, right-click in the *Search* view, select
|
|
|
6. If the changes are fine, right-click in the *Search* view, select
|
|
|
*Replace all*, and replace the current version string with the
|
|
|
update one:
|
|
|
- Add the new version number into the upcoming dialog and hit
|
|
|
“OK”
|
|
|
- Replace: “a.b.c”
|
|
|
- With: “d.e.f”
|
|
|
6. Use the file search again to find the containing text *a.b* (Current major version number, e.g.,
|
|
|
7. Use the file search again to find the containing text *a.b* (Current major version number, e.g.,
|
|
|
2.14). Manually replace the few search results which indeed use the old version number (attention: Not all results will need to be replaced - the search will likely also find false positives!).
|
|
|
7. Run a local build by selecting “Run As >Build All” and observe
|
|
|
8. Run a local build by selecting “Run As >Build All” and observe
|
|
|
if any error occurs.
|
|
|
8. If the build succeeds, commit the changes. **NOTE:** You must commit
|
|
|
9. If the build succeeds, commit the changes. **NOTE:** You must commit
|
|
|
to multiple repositories. Since these are submodules, you may need
|
|
|
to specify the remote branch: The issue number from the previously
|
|
|
created ticket shall be used.
|
|
|
9. Issue a MR for the plugin `org.fortiss.af3.root` and each of the
|
|
|
10. Issue a MR for the plugin `org.fortiss.af3.root` and each of the
|
|
|
submodules where there has been a version update.
|
|
|
10. After merging, ensure that the AF3 version is configured correctly. (Check maven releng repository for correct commit messages)
|
|
|
11. After merging, ensure that the AF3 version is configured correctly. (Check maven releng repository for correct commit messages)
|
|
|
|
|
|
### Update “What’s new” Page
|
|
|
|
... | ... | |