Hacktoberfest 2026: những issue maintainer đã đánh dấu cho tháng Mười, đang mở và phù hợp người mới. Xem issue Hacktoberfest

jdk25 upgrade

Đang mở
  • Có gì không ổn?
#3,904 1 bình luận 0 reaction 1 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 2 ngày

@shroffk đang làm issue này rồi.

Từ ngày 4/8/2026.

Đánh giá

Issue này chưa được đánh giá.

Mô tả

Summary

I am going to close the PR #3839 and re-approach this effort incrementally.

Right now, this migration is blocked by a mesh of related dependency and framework upgrades, and trying to land them in one PR introduces too much change at once for safe review and validation.

Problem

The current JDK 25 migration is not isolated. It pulls in a chain of related upgrades:

  • newer JavaFX requires JDK 25
  • Spring upgrade is needed for JDK 25 support
  • Jackson 3 upgrade is needed for the Spring upgrade path
  • Spring Security 6+ upgrade is needed as part of the Spring migration
  • Elasticsearch upgrade is needed for Jackson 3 compatibility
  • middle-layer service objects need updates, primarily for JSON/XML serialization and deserialization

Because of these dependencies, one PR ends up touching many layers of the system at once. That makes it difficult to:

  • review effectively
  • test confidently
  • identify regressions quickly
  • merge incrementally

Proposed approach

We should split this migration into a sequence of focused efforts instead of one large PR.

low-risk Spring service migration ( alarm-logger, alarm-config-logger )
  • migrate the lowest-complexity Spring service first
  • use that work to validate the Spring/JDK upgrade path
  • confirm compile, test, and packaging behavior before moving on
high-risk Spring service migration (save-restore)
  • migrate the most complex service last
  • handle:
    • Jakarta namespace changes
    • Spring Security updates
    • Elasticsearch compatibility
    • Jackson 3 integration
    • serialization/deserialization updates in service-layer objects
shared dependency reconciliation ( entire phoebus project )
  • reconcile shared/root Spring and related dependency versions
  • remove temporary overrides introduced during the transition
  • validate all Spring services together

Suggested work breakdown

This effort will likely need to be split across multiple PRs, including some combination of:

  • define and document the upgrade order for JDK 25, JavaFX, Spring, Jackson, Spring Security, and Elasticsearch
  • migrate low-risk Spring services first
  • upgrade Spring-dependent services iteratively
  • update Spring Security usage as required by the newer Spring line
  • update Jackson-related serialization/deserialization code
  • update Elasticsearch integration for compatibility
  • update middle-layer service objects impacted by JSON/XML mapping changes
  • run targeted testing after each step
  • run broader regression testing before final convergence on JDK 25

Notes

A more detailed upgrade analysis already exists and can be used as the implementation plan for follow-up issues/PRs, especially for:

  • Spring Boot upgrade sequencing
  • save-and-restore migration details
  • springdoc changes
  • Spring Security API updates
  • Elasticsearch/Jackson compatibility
  • Jakarta namespace migration
Ngôn ngữ chính
Java
Star
130
Fork
132
Merge trung bình
3 ngày 1 giờ
Pull request đã merge (30 ngày)
24

Chuẩn bị môi trường

  • Không có Dockerfile hay tệp Docker Compose
  • Có mẫu pull request
  • Không có hướng dẫn đóng góp

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của ControlSystemStudio/phoebus

Tất cả issue của ControlSystemStudio/phoebus

Issue tương tự

Thêm issue về Java

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.