Commit 1279286
authored
Change to how an empty or `null` jar manifest `ClassPath:` property is
handled:
in dotty.tools.dotc.classpath.ClassPathFactory:
- `classesInExpandedPath(...)` returns and empty `IndexedSeq` rather
than crash
- `isJarOrZip` returns `false` on a `null` reference rather than crash
in dotty.tools.dotc.classpath.FileUtils:
- `createSourcePath` fails with an error message on a `null` 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.
Closes #22461
1 file changed
+1
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
50 | 50 | | |
51 | 51 | | |
52 | 52 | | |
53 | | - | |
| 53 | + | |
54 | 54 | | |
55 | 55 | | |
56 | 56 | | |
| |||
0 commit comments