Skip to content

Migrate code generation operations to SubMonitor#3033

Closed
vogella wants to merge 1 commit into
eclipse-jdt:masterfrom
vogella:submonitor-phase1-codemanipulation
Closed

Migrate code generation operations to SubMonitor#3033
vogella wants to merge 1 commit into
eclipse-jdt:masterfrom
vogella:submonitor-phase1-codemanipulation

Conversation

@vogella

@vogella vogella commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Replaces the raw IProgressMonitor begin/done lifecycle and the Progress.subMonitor helper with SubMonitor.convert and split in four code generation operations: AddDelegateMethodsOperation, AddUnimplementedConstructorsOperation, GenerateHashCodeEqualsOperation and GenerateToStringOperation.

SubMonitor.convert handles null monitors and cleanup, so the explicit null guards and done() calls are no longer needed. This follows the canonical pattern from the Eclipse Progress Monitors article and continues the SubProgressMonitor/SubMonitor cleanup.

Builds cleanly and the dedicated source-action test suites (GenerateHashCodeEquals, AddUnimplementedConstructors, GenerateDelegateMethods, GenerateToString; 114 tests) pass.

Replace the raw IProgressMonitor beginTask/done lifecycle and the
Progress.subMonitor helper with SubMonitor.convert and split in four
code generation operations: AddDelegateMethodsOperation,
AddUnimplementedConstructorsOperation, GenerateHashCodeEqualsOperation
and GenerateToStringOperation.

SubMonitor.convert handles null monitors and cleanup, so the explicit
null guards and done() calls are no longer needed.
@vogella vogella closed this Jun 16, 2026
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