Skip to content

M3: forward MultiRule operations to the internal Rules owner - #14

Merged
hsoliwal merged 2 commits into
masterfrom
m3/eclipse-rules-forwarding-20261018
Oct 19, 2026
Merged

hsoliwal merged 2 commits into
masterfrom
m3/eclipse-rules-forwarding-20261018

Conversation

@hsoliwal

Copy link
Copy Markdown
Owner

Why

Move scheduling-rule combination behavior into the internal Java M3 owner while retaining the Eclipse Jobs facade and its existing calling contract.

What changes

  • MultiRule forwards all seven operations to org.eclipse.core.internal.jobs.m3.M3Rules.
  • The owner operates on the existing final child arrays. It preserves identity, duplicates, null handling, callback and exception ordering, one-level subclass projections, and the public descriptors.
  • The Jobs bundle remains JavaSE-17. The internal owner adds no exported API or Synexia runtime dependency.
  • Include the exact existing OpenRewrite recipe, four selected SDK source owners, original qualification evidence, and scoped provenance so this receiver can be reproduced from public sources.

The change set contains two actual recipe-generated runtime files and 74 proof/tooling/metadata files. It is composed on master 2bfb19847bd09bf28749194d489e8696b4a997b1, preserving the seven newer metadata/CI commits after the qualified source baseline. The exact intervening comparison changes none of the 76 receiver paths.

Validation

The committed qualification records real execution, including:

Gate Result
Existing OpenRewrite recipe 5 tests passed
Frozen client contracts 13 passed against baseline and candidate
Complete Jobs production sources 35 baseline / 36 candidate compiled with Java 21, release 17
Full-bundle contracts and unchanged upstream tests 16 passed against each variant, including 3 upstream tests
Public API and forwarding bytecode Identical public descriptors; 7 calls into M3Rules
Real Equinox external client 14 assertions passed against each variant

The 17-stage reproduction driver exited zero. A separate final shared-Text-owner compatibility run passed all five existing SDK tests and emitted the same two runtime files. This publication does not relabel source packaging checks as another execution of those gates.

The entire pre-existing Jobs bundle retains the same eight compiler warnings. Full diff whitespace checking reports 34 inherited findings in six byte-preserved license/raw-evidence files; all authored receiver metadata, both runtime outputs, and the other 70 paths pass. The scoped receipt identifies the preserved bytes.

Scope

This PR qualifies Rules ownership and forwarding. The scheduler, locks, other runtime services, and the complete Eclipse SDK build remain separate work. No unmeasured performance claim is made.

Canonical source: https://github.com/hsoliwal/com.synexia/pull/12357

Receiver and reproduction instructions: https://github.com/hsoliwal/eclipse.platform/tree/52f3d67e43402c5a65207109c2b37b68b5bbd74e/docs/M3-SCALE/rules-forwarding-20261018

Retain the public Jobs facade, array storage and callback contract while
moving all seven operations into M3Rules. Include the actual recipe
emissions, scoped public tooling mirror, and original qualification evidence.

Compose on the newer master to preserve the intervening recipe and CI work.
@hsoliwal
hsoliwal marked this pull request as ready for review October 19, 2026 04:13
@hsoliwal
hsoliwal merged commit 0708647 into master Oct 19, 2026
3 of 4 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.

1 participant