Jun 23, 2017 1:48:01 PM com.google.inject.internal.MessageProcessor visit
INFO: An exception was caught and reported. Message: org.reflections.ReflectionsException: Can't resolve member named 0 for class package.for.TestModule.lambda$someString
org.reflections.ReflectionsException: Can't resolve member named 0 for class package.for.TestModule..lambda$someString
Apparently the Reflections package counts the lambdas in the method as separate classes (which they are).
Thanks @ryonday. Seems like a weird bug, but at least you have a workaround :)
Happy to take a patch if you have one, but it might be a little while before I can take a look at it otherwise...
Let's make a module:
For some reason, we want to provide a String based on what's in the config (stupid example):
This will result in the following exception:
Apparently the Reflections package counts the lambdas in the method as separate classes (which they are).
This, however works: