-
Notifications
You must be signed in to change notification settings - Fork 935
-
Notifications
You must be signed in to change notification settings - Fork 935
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Class.forName can't find classes in sbt-1.3.0-RC1 #4760
Labels
area/classloader
issues around layered ClassLoader
Milestone
Comments
xerial
changed the title
Spark's class loader can't find some classes in sbt-1.3.0-RC1
Class.forName can't find classes in sbt-1.3.0-RC1
Jun 1, 2019
xerial
added a commit
to xerial/airframe
that referenced
this issue
Jun 1, 2019
xerial
added a commit
to xerial/airframe
that referenced
this issue
Jun 1, 2019
Use Class.forName with classloader
xerial
added a commit
to wvlet/airframe
that referenced
this issue
Jun 1, 2019
See #4769. |
Merged
xerial
added a commit
to wvlet/airframe
that referenced
this issue
Jun 13, 2019
This reverts commit f5d9dd8.
xerial
added a commit
to wvlet/airframe
that referenced
this issue
Jun 13, 2019
This reverts commit f5d9dd8.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
steps
I'm still trying to find a reproduction, but basically, a problem happens when using
Spark 2.4.x withScala 2.11, sbt-1.3.0-RC1.problem
Class.forName("(class name)")
-> causes java.lang.ClassNotFoundExceptionClass.forName("(class name)")
works without any problem.I guess some method (e.g.,
ClassLoader.getClassLoader(caller)
) used in Class.forName has an issue in sbt-1.3.0-RC1's layered class loader:expectation
notes
Class.forName(name, true, Thread.currentThread().getContextClassLoader())
instead ofClass.forName(name)
sbt version: 1.3.0-RC1
The text was updated successfully, but these errors were encountered: