-
Notifications
You must be signed in to change notification settings - Fork 337
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
improvement: if no binary version in jar path try using build target info #6698
Conversation
We could also try to check if there tasty files, but this is already a good improvement |
That's a better way to do this (though tasty files won't be in sources, so we have to map source jars to dep jars). |
…scala version for source jar
ddd69d3
to
087940c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aside from the naming comment LGTM!
@@ -434,10 +434,14 @@ final class BuildTargets private ( | |||
* @return path to the source jar for that jar | |||
*/ | |||
private def sourceJarPathFallback( | |||
sourceJarPath: AbsolutePath | |||
sourceJarPath: AbsolutePath, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We would probably need to rename the parameters and the method
@tgodzik @kasiaMarek what's holding up these changes? |
I'm afraid, I am. I need to address Tomek's review comment and it can be merged after that. |
For jars if no scala version included in the path, fallback to using scala version from build target before defaulting to "2.13".
resolves: #6693