Skip to content
Go to file

Latest commit

* Enable getMemberFromDescriptor to extract class names when methods have spaces

* Create

* Create

* Update

* Update pom.xml

* Updated FilterBuilder#excludePackage to use varargs; brings it in to line with includePackage.

* add repeatable annotation test

* wip fix'em ~all

* AbstractIterator to Iterator

* be minimal

* windows path

* maven release plugins

* predicate apply -> test

* MethodParameterNamesScanner - fix #256

* Use synchronized list to avoid concurrency failures

* Add unit test to reproduce issue

* Fix ConfigurationBuilder addClassLoaders

* fix custom url class loader test

* fix custom url class loader test

* fix custom url class loader test

* fix custom url class loader test

Co-authored-by: shyamz-22 <>
Co-authored-by: kudrevatykh <>
Co-authored-by: burkec <>
Co-authored-by: Honwhy Wang <>
Co-authored-by: ronma <ronma@>
Co-authored-by: merlin <>
Co-authored-by: Darío Cutillas <>

Git stats


Failed to load latest commit information.
Latest commit message
Commit time
Jun 22, 2019

Released org.reflections:reflections:0.9.12 - with support for Java 8

Reflections library has over 2.5 million downloads per month from Maven Central, and is being used by thousands of projects and libraries. We're looking for maintainers to assist in reviewing pull requests and managing releases, please reach out.

Java runtime metadata analysis, in the spirit of Scannotations

Reflections scans your classpath, indexes the metadata, allows you to query it on runtime and may save and collect that information for many modules within your project.

Using Reflections you can query your metadata such as:

  • get all subtypes of some type
  • get all types/members annotated with some annotation
  • get all resources matching a regular expression
  • get all methods with specific signature including parameters, parameter annotations and return type

Build Status


Add Reflections to your project. for maven projects just add this dependency:


A typical use of Reflections would be:

Reflections reflections = new Reflections("my.project");

Set<Class<? extends SomeType>> subTypes = reflections.getSubTypesOf(SomeType.class);

Set<Class<?>> annotated = reflections.getTypesAnnotatedWith(SomeAnnotation.class);


Basically, to use Reflections first instantiate it with urls and scanners

//scan urls that contain 'my.package', include inputs starting with 'my.package', use the default scanners
Reflections reflections = new Reflections("my.package");

//or using ConfigurationBuilder
new Reflections(new ConfigurationBuilder()
     .setScanners(new SubTypesScanner(), 
                  new TypeAnnotationsScanner().filterResultsBy(optionalFilter), ...),
     .filterInputsBy(new FilterBuilder().includePackage("my.project.prefix"))

Then use the convenient query methods: (depending on the scanners configured)

Set<Class<? extends Module>> modules = 
Set<Class<?>> singletons = 
Set<String> properties = 
Set<Method> resources =
Set<Constructor> injectables = 
Set<Field> ids = 
Set<Method> someMethods =
    reflections.getMethodsMatchParams(long.class, int.class);
Set<Method> voidMethods =
Set<Method> pathParamMethods =
List<String> parameterNames = 
Set<Member> usages = 
  • If no scanners are configured, the default will be used - SubTypesScanner and TypeAnnotationsScanner.
  • Classloader can also be configured, which will be used for resolving runtime classes from names.
  • Reflections expands super types by default. This solves some problems with transitive urls are not scanned.

Checkout the javadoc for more info.

Also, browse the tests directory to see some more examples.


ReflectionsUtils contains some convenient Java reflection helper methods for getting types/constructors/methods/fields/annotations matching some predicates, generally in the form of *getAllXXX(type, withYYY)

for example:

import static org.reflections.ReflectionUtils.*;

Set<Method> getters = getAllMethods(someClass,
  withModifier(Modifier.PUBLIC), withPrefix("get"), withParametersCount(0));

Set<Method> listMethodsFromCollectionToBoolean = 
    withParametersAssignableTo(Collection.class), withReturnType(boolean.class));

Set<Field> fields = getAllFields(SomeClass.class, withAnnotation(annotation), withTypeAssignableTo(type));

See more in the ReflectionUtils javadoc

Integrating into your build lifecycle

Although scanning can be easily done on bootstrap time of your application - and shouldn't take long, it is sometime a good idea to integrate Reflections into your build lifecyle. With simple Maven/Gradle/SBT/whatever configuration you can save all scanned metadata into xml/json files just after compile time. Later on, when your project is bootstrapping you can let Reflections collect all those resources and re-create that metadata for you, making it available at runtime without re-scanning the classpath.

For Maven, see example using gmavenplus in the reflections-maven repository

Other use cases

See the UseCases wiki page


Pull requests are welcomed!!

Apologize for not maintaining this repository continuously! We're looking for maintainers to assist in reviewing pull requests and managing releases, please reach out.

The license is WTFPL, just do what the fuck you want to.

This library is published as an act of giving and generosity, from developers to developers.

Please feel free to use it, and to contribute to the developers community in the same manner. Dāna Donate


You can’t perform that action at this time.