cailin186 / reflections

Automatically exported from code.google.com/p/reflections
Do What The F*ck You Want To Public License
0 stars 0 forks source link

not enough info when "could not get type for name XXX" exception is thrown from ReflectionUtils.forName #163

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Try loading classes via the Reflections.getSubTypesOf(Object.class), and 
have one of the classes import a third party class which isn't in the 
classpath. 

What is the expected output? What do you see instead?
I expect to see a message stating the missing class, such as an exception. The 
problem is that the exception in ReflectionUtils.forName is being caught and 
ignored. This is OK, since there is an attempt to load it via several class 
loaders.
However, after trying with all class loaders and failing, I'd like to see the 
actual exceptions that were thrown during those attempts. 

This can be done by collecting those Exceptions and setting them on the 
ReflectionsException that is thrown, or printing them right before throwing it.

What version of the product are you using? On what operating system?
I'm using the RC1 version 0.9.9, on linux.

Please provide any additional information below.
The code that I'm referring to is in org/reflections/ReflectionUtils.java,  
lines 369 - 378

Original issue reported on code.google.com by avizoh...@gmail.com on 27 Oct 2013 at 1:11

GoogleCodeExporter commented 9 years ago

Original comment by ronm...@gmail.com on 21 Dec 2013 at 9:37