Fix for #22461 Empty ClassPath attribute in one or more classpath jars causes crash #22462
+20
−12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change to how an empty or
null
jar manifestClassPath:
property is handled:in dotty.tools.dotc.classpath.ClassPathFactory:
classesInExpandedPath(...)
returns and emptyIndexedSeq
rather than crashisJarOrZip
returnsfalse
on anull
reference rather than crashin dotty.tools.dotc.classpath.FileUtils:
createSourcePath
fails with an error message on anull
file parameter.In the context of #22461, this causes an empty
ClassPath:
property to be treated the same as a mispelled or missing classpath entry, which are silently ignored, matching the behaviour of legacy scripts.