Proposed 4.28.0.Final-SNAPSHOT target platform change(s): Updated: lsp4mp 0.8.0 lsp4e 0.23.0 reddeer 4.6.0 swtbot 4.1.0 docker 5.11.0 webtools 3.30.0 cdt 11.2.0 tm 4.5.500 dtp 1.15.0 simrel 2023-06 GA m2e 2.3.0 orbit R for 4.28 wildwebdeveloper 1.1.1 eclipse 4.28 qute-jdt 0.15.0 quarkus-jdt 0.15.0 jgit 6.6.0...
by sbouchet＠redhat.com
Here is a proposal for change(s) to the JBoss Tools / Red Hat Central target platforms.
Affected Versions:
jbosstools 4.28.0.Final
jbt TPs 4.28.0.Final-SNAPSHOT
central TPs 4.28.0.AM1-SNAPSHOT
Detail / Summary:
Updated:
lsp4mp 0.8.0
lsp4e 0.23.0
reddeer 4.6.0
swtbot 4.1.0
docker 5.11.0
webtools 3.30.0
cdt 11.2.0
tm 4.5.500
dtp 1.15.0
simrel 2023-06 GA
m2e 2.3.0
orbit R for 4.28
wildwebdeveloper 1.1.1
eclipse 4.28
qute-jdt 0.15.0
quarkus-jdt 0.15.0
jgit 6.6.0
Related JIRA(s):
https://issues.redhat.com/browse/JBIDE-29030
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.28.0.Final-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.28.0.Final-SNAPSHOT -Dtpc.targetKind=multiple
For Central, fetch sources from jbosstools-discovery, then build as above.
----------
10 months, 1 week
ACTION REQUIRED: JBoss Tools triage time
by sbouchet＠redhat.com
As the current sprint 'Sprint #240' draws to a close, it is time
to review your unresolved issues!
Some may be done (or will be done soon), but the JIRA(s) need resolution.
Others may need to be pushed to the next milestone (4.29.0.Final,
to a future .x release, or LATER.
All unresolved issues for 4.28.0.Final:
https://issues.redhat.com/issues/?jql=project%20in%20(JBIDE)%20AND%20fixV...
All *YOUR* unresolved issues for 4.28.0.Final:
https://issues.redhat.com/issues/?jql=project%20in%20(JBIDE)%20AND%20fixV...
Once created, you can also begin scheduling your work for the upcoming
sprint, 'Sprint #241'.
Triage tips:
* blocker/critical issues: make these your priority work for the next sprint:
move to next version & assign to the next sprint
* other issues that WILL be done in the next sprint:
move to next version & assign to the forthcoming sprint, but lower down
* non-blocker & non-critical issues not for the next sprint:
move to .x (or LATER)
10 months, 1 week
