Purpose

Finds fully qualified Java class names whose simple (short) names match a Java regular expression. Use this tool when you know a class-name pattern but do not know the package, such as when looking for service, controller, or Maven Mojo implementations. It is commonly the discovery step before get-class-info.

Features

• Matches the regular expression against ClassInfo.getSimpleName(), not the package-qualified name.
• Searches classes visible through the Maven project's compile classpath, test output directory, and main output directory.
• Returns fully qualified names that can be passed to get-class-info.
• Rejects searches that produce more than 10 matches so that callers refine an overly broad pattern.
• Uses a cached scan for the registered project after its first class-related request; later source or configuration changes are not automatically reflected.

Input parameters

Result and errors

On success, the result is a list of fully qualified class-name strings. If there are no matches, the tool raises IllegalArgumentException with Class not found.. If more than 10 classes match, it raises IllegalArgumentException and reports the count and the maximum; narrow the pattern and try again. If project-dir has not been registered, it raises IllegalArgumentException with The project does not have classInfoProjectMap.. An invalid regular expression may also fail with the regular-expression compilation error.

Example

{
  "class-name": ".*Service",
  "project-dir": "C:/work/example"
}

This searches for classes whose simple names end in Service, for example com.example.user.UserService.

Purpose

Returns reflective metadata for a Java class identified by its fully qualified name. Use it after discovering a class, or when you already know the exact class name and need to understand its accessible API, inheritance, annotations, or origin.

Features

• Loads the class with a class loader built from the registered Maven project's compile classpath and output directories.
• Reports the class name, modifiers, superclass (when present), and directly implemented interfaces.
• Reports declared non-private fields and methods, including modifiers, types, names, and parameter types.
• Reports all declared constructors, including private constructors, with modifiers, name, and parameter types.
• Reports declared class annotations as strings.
• Reports the class's resolved directory or JAR path, dependency coordinates when available, and a matching source path when the class belongs to a compile source root.
• Uses the same cached project scan as find-class, so the metadata reflects the state when that scan was first initialized.

Input parameters

Result

On success, the tool returns a JSON-serializable object containing the following properties when applicable:

A missing class causes ClassNotFoundException. An unregistered project-dir causes IllegalArgumentException with The project does not have classInfoProjectMap..

Example

{
  "class-name": "org.example.MyService",
  "project-dir": "C:/work/example"
}

ClassFunctionalTools

ClassFunctionalTools implements FunctionTools and exposes the two callable operations. It maintains a map from Maven project base directories to ClassInfoHolder instances. A project can be registered through the constructor or scanProjectClasses(MavenProject). Each tool call uses project-dir to select the corresponding holder, extracts the requested class-name value, and either returns the result or reports an error.

ClassInfoHolder

ClassInfoHolder owns discovery for one Maven project. Its class discovery scan is lazy: the class loader and class list are initialized on the first class search, class load, or class-origin lookup. The loader is built from Maven compile-classpath elements plus the test and main output directories. Guava ClassPath then supplies the visible class list used by find-class. Source lookup is separate and checks the project's compile source roots while generating the sourcePath result property.

For origin metadata, the holder scans the main output directory and resolved Maven dependency artifacts. It records loadable public and protected classes, their directory or JAR path, and dependency coordinates. It searches compile source roots for source files and removes a nested-class suffix (for example, $Inner) before looking for the top-level .java file. Missing class paths are skipped and class entries that cannot be loaded are logged and ignored.