Skip to content

Sync fork with upstream eclipse-jdt/eclipse.jdt.debug#33

Merged
carstenartur merged 190 commits intomasterfrom
copilot/merge-upstream-changes
Dec 7, 2025
Merged

Sync fork with upstream eclipse-jdt/eclipse.jdt.debug#33
carstenartur merged 190 commits intomasterfrom
copilot/merge-upstream-changes

Conversation

Copy link
Copy Markdown

Copilot AI commented Dec 7, 2025

Brings fork up-to-date with upstream master by merging 10,693 commits.

Merge Strategy

Used --allow-unrelated-histories -X theirs to resolve 298 conflicts. Fork had grafted history; theirs strategy accepts all upstream changes to achieve full sync.

Key Changes from Upstream

Modified Files

464 files changed:

  • All module MANIFEST.MF versions updated (e.g., org.eclipse.jdt.debug: 3.25.0.qualifier)
  • pom.xml parent version: 4.39.0-SNAPSHOT
  • New test resources for Java 23-25
  • GitHub workflows aligned with upstream patterns

Build Requirements

Requires eclipse-platform-parent (4.39.0-SNAPSHOT) for full Maven build. Standard Eclipse plugin development setup works as-is.

Original prompt

Bitte erstelle einen Pull Request, der den Fork carstenartur/eclipse.jdt.debug wieder auf den neuesten Stand bringt, indem er die Änderungen aus dem Upstream-Repository eclipse-jdt/eclipse.jdt.debug in diesen Fork integriert. Details und Aufgaben:

  • Basis-Branch: master (Ziel: merge/up-to-date)
  • Upstream-Quelle: eclipse-jdt/eclipse.jdt.debug (standard branch des Upstreams)
  • Erstelle einen PR, der die Upstream-Änderungen in den Fork-Master merged. Wenn es Konflikte gibt, löse sie so, dass:
    • Build und Kompilierung für die vorhandene Java/Eclipse-Projektstruktur wieder funktionieren
    • Tests (falls vorhanden) erfolgreich laufen
    • Lizenzhinweise (EPL-2.0) und Copyright-Header im Code erhalten bleiben
  • Führe lokale Anpassungen durch, falls sich Package-Namen, API-Änderungen oder Dependenzen im Upstream geändert haben, damit die Kompilierung wiederhergestellt wird. Dokumentiere in der PR-Beschreibung alle größeren Änderungen und Entscheidungen zur Konfliktlösung.
  • Falls nötig, passe CI/Build-Dateien an (z. B. Maven/Gradle/Ant/CI-Workflow), damit der PR-Check grün wird.

Bitte öffne den PR in diesem Repository (carstenartur/eclipse.jdt.debug) und schreibe eine prägnante PR-Beschreibung auf Deutsch mit den wichtigsten Änderungen, evtl. verbleibenden offenen Punkten und Anweisungen zum Testen.

Wenn du weitere spezifische Branches aktualisieren sollst (z. B. R3_6_maintenance, R3_5_maintenance oder BETA_JAVA*), sag mir kurz welche Branches priorisiert werden sollen oder bestätige, dass nur master aktualisiert werden soll.

This pull request was created as a result of the following prompt from Copilot chat.

Bitte erstelle einen Pull Request, der den Fork carstenartur/eclipse.jdt.debug wieder auf den neuesten Stand bringt, indem er die Änderungen aus dem Upstream-Repository eclipse-jdt/eclipse.jdt.debug in diesen Fork integriert. Details und Aufgaben:

  • Basis-Branch: master (Ziel: merge/up-to-date)
  • Upstream-Quelle: eclipse-jdt/eclipse.jdt.debug (standard branch des Upstreams)
  • Erstelle einen PR, der die Upstream-Änderungen in den Fork-Master merged. Wenn es Konflikte gibt, löse sie so, dass:
    • Build und Kompilierung für die vorhandene Java/Eclipse-Projektstruktur wieder funktionieren
    • Tests (falls vorhanden) erfolgreich laufen
    • Lizenzhinweise (EPL-2.0) und Copyright-Header im Code erhalten bleiben
  • Führe lokale Anpassungen durch, falls sich Package-Namen, API-Änderungen oder Dependenzen im Upstream geändert haben, damit die Kompilierung wiederhergestellt wird. Dokumentiere in der PR-Beschreibung alle größeren Änderungen und Entscheidungen zur Konfliktlösung.
  • Falls nötig, passe CI/Build-Dateien an (z. B. Maven/Gradle/Ant/CI-Workflow), damit der PR-Check grün wird.

Bitte öffne den PR in diesem Repository (carstenartur/eclipse.jdt.debug) und schreibe eine prägnante PR-Beschreibung auf Deutsch mit den wichtigsten Änderungen, evtl. verbleibenden offenen Punkten und Anweisungen zum Testen.

Wenn du weitere spezifische Branches aktualisieren sollst (z. B. R3_6_maintenance, R3_5_maintenance oder BETA_JAVA*), sag mir kurz welche Branches priorisiert werden sollen oder bestätige, dass nur master aktualisiert werden soll.


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

SougandhS and others added 30 commits September 30, 2024 13:37
Openjdk jdk is not kept uptodate.
Set up for this repository the workflow for automated version increments
in pull-requests added via
eclipse-platform/eclipse.platform.releng.aggregator#2352
As the test skips compilation of the code only when run on Java 19+
there is no need to hardcode release but rather let the JVM use it's
default.
Skip getting and passing default DiagnosticCollector as the compiler
will do that when passed null.
GH provides it as standard option in the UI.
Was ArrayIndexOutOfBoundsException in fEventListeners.elementAt()

eclipse-jdt#527
…clipse-jdt#532)

The content is based on the content of the corresponding files in
jdt.core/ui.
Additionally add a styled and drag&drop-able Oomph Configuration button
to the main README.

Part of eclipse-platform/eclipse.platform.releng.aggregator#2430
The JDK detection mechanism doesn't find much on Windows. Have it find
the default installation directories of Adoptium and RedHat. Further
providers can easily be added without changing the code logic.

Also let duplicate VM names start with index 2, not 1. And finally
improve the job name.
signature + code review changes + Additional changes"

This reverts commit 32fa010.

Added code is unmaintainable and has multiple regressions. It should
have never been merged "as is".

See eclipse-jdt#544
Fixes eclipse-jdt#543
+ Start the BETA_JAVA24 branch
+ recognize JavaSE-24
+ bump version by +50

Fixes eclipse-jdt#551
+ Move all test infra for Java 23 to 24, all use enable-preview
+ create extension for EE JavaSE-24
+ allow PR build to access the Y-Builds repository
This commit adds a waiting time to ensure value is received prior
invoking getHyperLink method as there is a possibility for throwing NPE

Fixes : eclipse-jdt#559
The change in 3530050 replaced
JDIDebugUIPlugin.getActiveWorkbenchShell() with
PlatformUI.getWorkbench().getModalDialogShellProvider().getShell(),
however later one behavior is undefined in API but implementation
requires the caller to be in UI thread - which was not the case of the
former API.

=> Move the code that acquires the modal shell into UI thread.

Fixes eclipse-jdt#563
Performed manual code cleanup in pattern matching using
instanceof operator according to Java 16 guidelines,
making the code more concise for classes in jdt.launching package.
…jdt#570

When trying to open breakpoint Preferences page "Filtering"

JavaBreakpointAdvancedPage is referenced by:
org.eclipse.jdt.debug.ui\plugin.xml

partial revert of
1e0e94b

eclipse-jdt#570
laeubi and others added 21 commits September 27, 2025 13:45
Currently when one launches a multi-release compiled project one always
gets the type from the default project folder.

This now first checks what JRE is used to launch, then adds all valid
folders in reverse version order to the classpath to emulate the
behavior of loading a multi-release jar at runtime.

Fix https://github.com/eclipse-jdt/eclipse.jdt.core/issues/4276
…clipse-jdt#787)

Add null check in JavaTestPlugin.getFileInPlugin(IPath) to prevent NPE when path cannot be converted to a file

Fixes : eclipse-jdt#786
Signed-off-by: David Thompson <davthomp@redhat.com>
For whatever reason original change added listener on thread termination
and not on target termination event, and for whatever reason it wasn't
noticed during review.

Fixing that. HCR dialog should only close automatically if the debug
target is terminated, not if some thread in the target is terminated.

Fixes eclipse-jdt#792
Allow users to put a lambda entry breakpoint on a selected lambda if
line contains multiple chained lambda expressions.

Fixes : eclipse-jdt#732

Co-authored-by: Andrey Loskutov <loskutov@gmx.de>
Due to eclipse-jdt/eclipse.jdt.core#4293 ecj
no longer warnigs about using a method inherited from a deprecated type
Fixes remaining `@SuppressWarnings("deprecation")` annotations flagged
as unnecessary by
eclipse-jdt/eclipse.jdt.core#4564

See eclipse-jdt/eclipse.jdt.core#4553
Add @deprecated to members of truly deprecated classes
+ most classes have a replacement for a long time already
+ still in use and no replacement specified:
  - JavaSourceLocationWorkbenchAdapterFactory
…clipse-jdt#803)

Enabling exit will make debugger suspend at random lambdas and by default lambda method breakpoints are already enabled
These files are generated during SDK build and make the working tree
dirty after the build:

```
git status
On branch master
Untracked files:
  (use "git add <file>..." to include in what will be committed)
        org.eclipse.jdt.debug.tests/javadebugtests.jar
        org.eclipse.jdt.debug/jdimodel.jar
```
This avoids unexpected tracing output from
JREContainerInitializer.resolveVM(IPath) if tracing is not enabled.
Avoid adding Watch Expressions when the input snippet is empty. This
prevents unnecessary entries from appearing in the Expressions view and
improves overall usability.
…se-jdt#812)

Highlights the specific lambda in the source when a lambda stack frame
is selected by introducing a new lambda stackframe adapter
Copilot AI changed the title [WIP] Merge upstream changes from eclipse-jdt/eclipse.jdt.debug Sync fork with upstream eclipse-jdt/eclipse.jdt.debug Dec 7, 2025
Copilot AI requested a review from carstenartur December 7, 2025 15:25
@carstenartur carstenartur marked this pull request as ready for review December 7, 2025 15:43
@carstenartur carstenartur merged commit ff24088 into master Dec 7, 2025
5 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.