Here is a proposal for change(s) to the JBoss Tools / Red Hat CodeReady Studio / Red Hat
Central target platforms.
Affected Versions:
jbosstools 4.17.0.AM1
devstudio 12.17.0.AM1
jbt/ds TPs 4.17.0.AM1-SNAPSHOT
central TPs 4.17.0.AM1-SNAPSHOT
Detail / Summary:
orbit;S20200727174946
simrel;20200717-1000-Simrel.2020-09
m2e;1.16.1.20200710-1008
jetty;9.4.30.v20200611
lsp4mp;0.0.9.20200714-1747
jdtls;0.60.0.202007230941
scout;4.0-testing
wildwebdeveloper;0.11.0
lsp4e;0.13.3.202007281439
webtools;3.19.0.M2
docker;5.0.0.202008042201
mylyn;3.26.0
testng;7.3.0.202008060412
camel-lsp;1.0.0.202007220638
reddeer;3.1.0.M2
Related JIRA(s):
https://issues.jboss.org/browse/JBIDE-27429
Pull Request(s):
(already merged - see related JIRA(s))
https://github.com/jbosstools/jbosstools-target-platforms/pull/361
p2diff Report(s):
(will attach to JIRA when available)
----------
Please review the above changes, as they have been applied and are building today.
Once the target platform is built, jobs and parent pom will be updated to point
TARGET_PLATFORM_VERSION_MAX at the new version, 4.17.0.AM1-SNAPSHOT.
You can use the following to build & test the target platforms locally against
your component(s).
Build target-platform:
cd /path/to/jbosstools-target-platforms
git fetch origin pull/<pull-request-number>/head && git checkout
FETCH_HEAD
# or, using hub for git
git checkout <pull-request-URL>
mvn clean install -f jbosstools/multiple/pom.xml
Then, to test the new multiple target platform against your component's build:
cd /path/to/your/jbosstools-component
mvn clean verify -Dtpc.version=4.17.0.AM1-SNAPSHOT -Dtpc.targetKind=multiple
For Central, fetch sources from jbosstools-discovery, then build as above.
----------