Bundlor's main function is to scan an existing JAR file and determine its runtime dependencies. With this information it can then generate the OSGi-compliant manifest headers needed for proper runtime operation. This analysis is comprised of looking for class references and class names in Java classes and certain well-known file types.
Bundlor scans any Java class it can find in the artifact created by the underlying build system. This means
that if a build process has custom behavior (i.e. weaving with AspectJ or
Bundlor will be able to see and analyze the changes made by that process as long as the changes are in the
artifact created by the build system.
There are a number of places in a Java class that another Java type can be referenced from. Bundlor detects these references and adds manifest requirements for them.
The following is a list of the places that Bundlor will search for type names