[jbosstools-dev] Proposed 4.27.0.AM1-SNAPSHOT target platform change(s): updated eclipse I20230215-1800-M3 reddeer 4.5.0.M2 docker 5.10.0.202302212217 webtools S-3.29M3-20230220000017 jetty 10.0.13 cdt 11.0.0 simrel 202302241001-Simrel.2023-03-M3 m2e-wtp 1.6.0 orbit S20230214193619 jgit 6.5.0.202302221508-m3...
Here is a proposal for change(s) to the JBoss Tools / Red Hat Central target platforms.
Affected Versions:
jbosstools 4.27.0.AM1
jbt TPs 4.27.0.AM1-SNAPSHOT
central TPs 4.27.0.AM1-SNAPSHOT
Detail / Summary:
updated
eclipse I20230215-1800-M3
reddeer 4.5.0.M2
docker 5.10.0.202302212217
webtools S-3.29M3-20230220000017
jetty 10.0.13
cdt 11.0.0
simrel 202302241001-Simrel.2023-03-M3
m2e-wtp 1.6.0
orbit S20230214193619
jgit 6.5.0.202302221508-m3
Related JIRA(s):
https://issues.redhat.com/browse/JBIDE-28878
Pull Request(s):
(already merged - see related JIRA(s))
p2diff Report(s):
attached to JIRA
----------
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.27.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.27.0.AM1-SNAPSHOT -Dtpc.targetKind=multiple
For Central, fetch sources from jbosstools-discovery, then build as above.
----------