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

Add proper output option for the forked Java compiler #1694

Merged
merged 1 commit into from
Feb 24, 2022

Conversation

tgodzik
Copy link
Contributor

@tgodzik tgodzik commented Feb 23, 2022

Previously, we only added the output directory for the local Java compiler, which caused compile artifacts to pop up in the source directories. Now, we properly add the output directory option.

Fixes #1691

I also removed 2 tests that were commented out for a long while.

@tgodzik tgodzik requested a review from kpodsiad February 23, 2022 15:26
) ::: moreOptions
else moreOptions
if (project.javaVersionAtLeast("17", logger))
List(
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Let's only add the additional options if we are the ones adding java semanticdb plugin. Otherwise if it's done manually then it need to be properly configured by the user

Previously, we only added the output directory for the local Java compiler, which caused compile artifacts to pop up in the source directories. Now, we properly add the output directory option.

Fixes scalacenter#1691
@tgodzik tgodzik merged commit 3cc4983 into scalacenter:main Feb 24, 2022
@tgodzik tgodzik deleted the fix-ouput-forked branch February 24, 2022 12:43
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.

class and semanticdb files in wrong place and javacOptions repeated for java only + jdk 17
2 participants