On 03/03/2016 08:48, Rory O'Donnell wrote:
Alex,
Sure, I will try to reach out to them.
If you or anyone on the list has contacts they can share with me that
would be great.
Rgds,Rory
I don't know have contacts but just to add to Alex's mail where he said:
"The concern is whether these tools make assumptions about the JDK's
class loader hierarchy (Gradle was hit by this) and the JDK classes
loaded by each loader (Eclipse was hit by this). "
It is important to flush out these issues. In the Gradle case then it
assumed the system class loader is a URLClassLoader [1]. In the Eclipse
case then it seems to be delegating directly to the boot loader and so
was tripped up by changes to move non-core classes out of the boot
loader [2].
I don't like pointing out specific issue in other tools/libraries of
course but they are useful examples that other projects might relate to.
I have no doubt that there will be more of these cases like this,
particularly the latter as we have moved many non-core modules,
including all of the "morally EE" modules, to the extension class loader.
-Alan
[1] https://issues.gradle.org/browse/GRADLE-3287
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=466683
