This message was deleted.
# plugin-development
s
This message was deleted.
e
even
processIsolation
will extend the current classpath (with
Parameters
serialized and deserialized across the process boundary), so I don't think there's any way built-in
m
thanks!
e
javaexec
will start with a whole new classpath I guess, although you have to set that up yourself
maybe you could create your own classloader inside a
noIsolation
worker
👀 1
m
Ah, good idea! I'll try that.
Never really created my own classloader but I guess there's a first time to everything 😄
e
by which I mean like
Copy code
URLClassLoader(jars.map { it.toURI().toURL() }.toTypedArray(), ClassLoader.getSystemClassLoader())
👀 1
🙏 1
m
Thanks, I'll dig into this 👍
t
Martin, i have an example of creating my own classloader in the dependency analysis plugin too
💙 1
m
Guessing around here?
👍 1
c
An alternate solution to forming an entirely new classloader from URLs might be to have a classloader that is a child of the regular loader with a delegation model that is a function of the class/package name 😄
👍 1
easier to special case the things you want to isolate, but leave everything else working as before.
t
my classloader has an inverted delegation model, so i second the notion 😄
👍 1