Proposed 4.27.0.Final-SNAPSHOT target platform change(s): updated: eclipse R-4.27-202303020300 wildwebdeveloper 1.0.3 lsp4e 0.22.0 reddeer 4.5.0 docker 5.10.0.202303072327 webtools R-3.29.0-20230303230236 cdt 11.1.0 simrel 202303151000-Simrel.2023-03 m2e 2.2.1 orbit R20230302014618 jgit 6.5.0.202303070854-r...
by sbouchet＠redhat.com
Here is a proposal for change(s) to the JBoss Tools / Red Hat Central target platforms.
Affected Versions:
jbosstools 4.27.0.Final
jbt TPs 4.27.0.Final-SNAPSHOT
central TPs 4.27.0.Final-SNAPSHOT
Detail / Summary:
updated:
eclipse R-4.27-202303020300
wildwebdeveloper 1.0.3
lsp4e 0.22.0
reddeer 4.5.0
docker 5.10.0.202303072327
webtools R-3.29.0-20230303230236
cdt 11.1.0
simrel 202303151000-Simrel.2023-03
m2e 2.2.1
orbit R20230302014618
jgit 6.5.0.202303070854-r
Related JIRA(s):
https://issues.redhat.com/browse/JBIDE-28903
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.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.27.0.Final-SNAPSHOT -Dtpc.targetKind=multiple
For Central, fetch sources from jbosstools-discovery, then build as above.
----------
1 year, 1 month
ACTION REQUIRED: JBoss Tools triage time
by sbouchet＠redhat.com
As the current sprint 'Sprint #233' 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 (X.Y.Z.QUAL,
to a future .x release, or LATER.
All unresolved issues for X.Y.Z.QUAL:
https://issues.redhat.com/issues/?jql=project%20in%20(JBIDE)%20AND%20fixV...
All *YOUR* unresolved issues for X.Y.Z.QUAL:
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 #234'.
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)
1 year, 1 month
