Skip to content

Conversation

@rcosta358
Copy link
Collaborator

@rcosta358 rcosta358 commented Nov 21, 2025

Added a condition in the CommandLineLauncher that reports a warning if the Java compilation fails, to alert the user that the LiquidJava verification might be affected by it. Added a custom warning class for this case.

boolean buildSuccess = launcher.getModelBuilder().build();
if (!buildSuccess) {
diagnostics.add(new CustomWarning("Java compilation error detected. Verification might be affected."));
}

When using the LiquidJava extension, this warning is only visible in the problems tab and in the webview, not in the editor itself, since we can't provide a location for the error.

image

This approach is not ideal since a compilation error in a single file causes the whole verification to be skipped for the whole directory.
@rcosta358 rcosta358 changed the title Java Compilation w Java Compilation Warning Nov 21, 2025
@rcosta358 rcosta358 self-assigned this Nov 21, 2025
@rcosta358 rcosta358 added the enhancement New feature or request label Nov 21, 2025
Copy link
Collaborator

@CatarinaGamboa CatarinaGamboa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great! Thanks

launcher.getEnvironment().setComplianceLevel(8);
launcher.run();

boolean buildSuccess = launcher.getModelBuilder().build();
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This always feels like magic trying to find the right words haha

@rcosta358 rcosta358 merged commit d4ef259 into main Nov 21, 2025
1 check passed
@rcosta358 rcosta358 deleted the check-java-compilation branch December 4, 2025 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants