Repository navigation
M3: forward MultiRule operations to the internal Rules owner - #14
Merged
Merged
Conversation
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
marked this pull request as ready for review
October 19, 2026 04:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
MultiRuleforwards all seven operations toorg.eclipse.core.internal.jobs.m3.M3Rules.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:
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