eclipse-sailing-analytics/sailing-analytics
1
0
Fork 0
mirror of https://github.com/eclipse-sailing-analytics/sailing-analytics.git synced 2026-09-19 12:15:28 +00:00
Code Activity

Merge remote-tracking branch 'server/master'

Browse Source
This commit is contained in:
Axel Uhl
2020-11-09 23:15:38 +01:00
parent 6901fccd54 46f15cc6dd
commit fb48f987b5
6 changed files with 355 additions and 228 deletions
Download Patch File Download Diff File Expand all files Collapse all files
java/com.sap.sailing.feature.p2build/scripts/README
+1 -1
View File
@@ -6,5 +6,5 @@ what is defined in the .product file.
Example usage:
analyzeProduct.sh ../raceanalysis.product ../../com.sap.sailing.server/SailingServer\ \(No\ Proxy\,\ GENERATED\).launch
updateEclipseLaunchers.sh ../raceanalysis.product ../../com.sap.sailing.server/SailingServer\ \(No\ Proxy\,\ GENERATED\).launch
java/com.sap.sailing.feature.p2build/scripts/analyzeProduct.sh → java/com.sap.sailing.feature.p2build/scripts/updateEclipseLaunchers.sh
+1 -1
View File
@@ -1,5 +1,5 @@
#!/bin/bash
# Call like this: analyzeProduct.sh <my.product> [<my.launch> ...]
# Call like this: updateEclipseLaunchers.sh <my.product> [<my.launch> ...]
# Updates Eclipse .launch files with the bundles needed for starting an SAP Sailing server based on the current feature.xml.
# The .launch files must be in the workspace format that was introduced with Eclipse 2019-12. The script prints an error when no matching
# replacement section could be found.
java/com.sap.sailing.feature.p2build/scripts/updateSeleniumPom.sh
+1 -1
View File
@@ -1,5 +1,5 @@
#!/bin/bash
# Call like this: analyzeProduct.sh <my.product> <path-to-java/com.sap.sailing.selenium.test/pom.xml>
# Call like this: updateSeleniumPom.sh <my.product> <path-to-java/com.sap.sailing.selenium.test/pom.xml>
# Will patch the bundleStartLevel section in the pom.xml file so that all auto-start bundles
# configured in the product specification are also launched properly and with the correct start level
# for the Selenium tests.