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

Use semanticdb files directly in ScalaModule #3078

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

lolgab
Copy link
Member

@lolgab lolgab commented Mar 11, 2024

A copy mechanism was introduced in #2227 because of a bug in semanticdb-java
But we don't need to use it in ScalaModule as well if the Scala semanticdb works correctly.

A copy mechanism was introduced in com-lihaoyi#2227
because of a bug in semanticdb-java
But we don't need to use it in ScalaModule as well
if the Scala semanticdb works correctly.
@lolgab lolgab requested a review from lefou March 11, 2024 14:16
@lolgab lolgab force-pushed the avoid-copy-semanticdb-scala branch from 494cac1 to 2b41c5c Compare March 11, 2024 14:39
@lefou
Copy link
Member

lefou commented Mar 19, 2024

There are test failures.

Also, I'd like to get PR #3080 in before, which brings additional test for incremental semanticDB generation.

Copy link
Member

@lefou lefou left a comment

Choose a reason for hiding this comment

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

The copy operation isn't the only functionality of copySemanticDbFiles. It also ensures, we return a path with onlysemanticdb files in it. Your change returns the complete compiler output directory, which may contain class files and other auxiliary files.

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