What steps will reproduce the problem?
1. Create two classes like this:
package test;
import org.junit.Runner.RunWith;
@RunWith(JUnit4.class)
public class ParentClass {
}
public class ChildClass {
}
2. Create a Reflections such that java.lang.annotation.Inherited is either
filtered out or is not present in the URLs:
Reflections reflections = new Reflections(
new ConfigurationBuilder()
.setUrls(ClasspathHelper.forPackage("test"))
.filterInputsBy(whatever)
);
//Note that EITHER the setUrls or filterInputsBy line will cause this problem.
3. Make a query that involves inheritance:
results = reflections.getTypesAnnotatedWith(RunWith.class, true);
What is the expected output? What do you see instead?
I would expect results to include ChildClass. Instead, I see only ParentClass.
What version of the product are you using? On what operating system?
0.9.5
Please provide any additional information below.
It appears to be because the Store uses its own filtered database to check on
Inherited being present.
Original issue reported on code.google.com by yarbro...@google.com on 22 Jan 2013 at 11:04
Original issue reported on code.google.com by
yarbro...@google.com
on 22 Jan 2013 at 11:04