d7a94ef8c47c72a130b64c2d7c5d519629d81126
wiki/info/landscape/typical-development-scenarios.md
| ... | ... | @@ -26,7 +26,8 @@ Bundle-Version: 3.6.4 |
| 26 | 26 | * Currently this scripts work for the cygwin shell and the git bash, if the path to your files in the target definition is incorrect, this may be the reason. |
| 27 | 27 | * Test the new overall target platform |
| 28 | 28 | * by setting the race-analysis-p2-local.target as target platform in the IDE |
| 29 | - * by running the local maven build via ''buildAndUpdateProduct.sh -v build'' (the ''-v'' switch builds and uses the local p2 repository) |
|
| 29 | + * by running the ``release`` workflow on Github using the "Build with a local target platform (set to "true" to use local target platform)" switch, or |
|
| 30 | + * run the local maven build via ''buildAndUpdateProduct.sh -v build'' (the ''-v'' switch builds and uses the local p2 repository) |
|
| 30 | 31 | * The admin of the central p2 repository (currently at sapsailing.com) must now replace the content of the central server /home/trac/p2-repositories/sailing with the content of the new local base p2 repository (com.sap.sailing.targetplatform.base/target/repository), using the 'uploadRepositoryToServer.sh' script |
| 31 | 32 | * Reload the target platform in the IDE |
| 32 | 33 |