File tree Expand file tree Collapse file tree 1 file changed +2
-12
lines changed Expand file tree Collapse file tree 1 file changed +2
-12
lines changed Original file line number Diff line number Diff line change 28
28
; ; this simply entails having the corresponding source artifacts in the
29
29
; ; project's dev dependencies. The core Java API classes are the exception to
30
30
; ; this, since these are external to lein/maven dependency management. For
31
- ; ; these, we search the JDK directory and add the source classpath entry
31
+ ; ; these, `enrich-classpath` searches the JDK directory and add the source classpath entry
32
32
; ; manually, if available. Prior to JDK9, parsing source files also requires
33
- ; ; having `tools.jar` on the classpath, which we'll have to add as well.
34
- ; ;
35
- ; ; The context classloader may be different at startup and in a
36
- ; ; REPL (e.g. nREPL) session, and these classloaders may not share a modifiable
37
- ; ; ancestor classloader. That's why the current implementation checks that the
38
- ; ; JDK sources are visible on the classpath prior to invoking the Java parser,
39
- ; ; and if not, adds a classpath entry for them. (see `ensure-jdk-sources`)
40
- ; ;
41
- ; ; An alternative approach would be to pass the REPL's classloader to Orchard's
42
- ; ; functions that modify the classpath. You can find a more extensive discussion
43
- ; ; on that topic here https://github.com/clojure-emacs/orchard/issues/103.
33
+ ; ; having `tools.jar` on the classpath.
44
34
45
35
(defn ^:deprecated jdk-find
46
36
" Search common JDK path configurations for a specified file name and return a
You can’t perform that action at this time.
0 commit comments