Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix java compile warning, again #3762

Merged
merged 20 commits into from
Oct 17, 2024

Conversation

lihaoyi
Copy link
Member

@lihaoyi lihaoyi commented Oct 17, 2024

Follow up to #3711

I swear this annotation didn't work last time, and the match on the discoveredModuleType did. But now they don't. Must have been getting confused by incremental compilation

Turns out the discover macro was incorrectly traversing type members and picking up their types, which is why it was appeared in the generated code, so I added a filter to filter them out

Added a test to assert on the full stdout/stderr of a simple mill command run to ensure we don't have stray logs or warnings turning up

@@ -79,7 +79,7 @@ jobs:

# Most of these integration tests should not depend on which mode they
# are run in, so just run them in `local`
- java-version: '11'
- java-version: '17'
Copy link
Member Author

Choose a reason for hiding this comment

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

The new test emits some benign warnings on Java 11, so just run on java 17 instead

@lihaoyi lihaoyi merged commit 0fdfdbb into com-lihaoyi:main Oct 17, 2024
24 checks passed
@lefou lefou added this to the 0.12.0 milestone Oct 17, 2024
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.

2 participants