Ólafur Páll Geirsson

@Marcuse7 Thank you for this contribution!

Thank you for reporting! I'm able to reproduce. A workaround is to include the argument `--output=dump.lsif` in the command ``` scip-java index --output=dump.lsif ``` We haven't fully reached feature parity...

I think the expected behavior would be to omit that occurrence for the same reason we no longer emit `this.` occurrences. We should still keep `super()` references to constructors.

Blocked by https://github.com/sourcegraph/sourcegraph/issues/27403

Thank you for reporting! The flag `-build-tool:sbt` is needed alongside `-sourceroot` and `-targetroot` to work with with the custom sbt file system https://github.com/sourcegraph/lsif-java/blob/205dc612578dbf4ef58b1444f65dba38adbea24b/semanticdb-javac/src/main/java/com/sourcegraph/semanticdb_javac/SemanticdbJavacOptions.java#L57 This flag is automatically added by sbt-sourcegraph...

Buck supports a `javac` option that might provide a way for `lsif-java` to inject the missing compiler options, similar to how we support Maven https://buck.build/files-and-dirs/buckconfig.html#tools.javac

@simonkoeten-wk Thank you for sharing your interest in this feature. There has been no update on this front, and it's not in our near-term roadmap to add automatic indexing support...

Thank you for reporting! This is exciting. > maybe having built-in support for index would help Is there a way to automatically detect which files are compiled with scala-cli? We...

I started working on this here https://github.com/sourcegraph/lsif-java/compare/main...olafurpg:raw-classpath?expand=1 but will need to pick up again later. Not sure how to structure the docs yet.

@jeremyrsmith whoops, you're right! I fixed the issue title.