Skip to content

Warn when .java & .scala sources are used in a mixed compilation with --server=false#4181

Draft
Gedochao wants to merge 1 commit intoVirtusLab:mainfrom
Gedochao:fix/3897-mixed-java-scala-compilation-no-server-warning
Draft

Warn when .java & .scala sources are used in a mixed compilation with --server=false#4181
Gedochao wants to merge 1 commit intoVirtusLab:mainfrom
Gedochao:fix/3897-mixed-java-scala-compilation-no-server-warning

Conversation

@Gedochao
Copy link
Contributor

@Gedochao Gedochao commented Mar 13, 2026

Fixes #3897

Checklist

  • tested the solution locally and it works
  • ran the code formatter (scala-cli fmt .)
  • ran scalafix (./mill -i __.fix)
  • ran reference docs auto-generation (./mill -i 'generate-reference-doc[]'.run)

How much have your relied on LLM-based tools in this contribution?

extensively, Claude + Cursor

How was the solution tested?

unit & integration tests provided

Additional notes

It doesn't make sense to error outright here, as the .java files still pass through the Java parser step in the compiler, which may be useful to a power user (well, chiefly to a compiler engineer, but still)

@Gedochao Gedochao force-pushed the fix/3897-mixed-java-scala-compilation-no-server-warning branch 3 times, most recently from 13913f4 to 88d462a Compare March 13, 2026 14:47
@Gedochao Gedochao force-pushed the fix/3897-mixed-java-scala-compilation-no-server-warning branch from 88d462a to f24d4fd Compare March 13, 2026 14:48
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.

Missing a meaningful error message when trying to pass non-Scala inputs with --server=false

1 participant