Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Erroneous package indexing with custom ClassIndexProcessor.indexPackages #81

Open
MrRoGue opened this issue Feb 29, 2024 · 0 comments
Open

Comments

@MrRoGue
Copy link

MrRoGue commented Feb 29, 2024

The documentation recommends to subclass org.atteo.classindex.processor.ClassIndexProcessor if you want to customize the ClassIndexProcessing. By setting custom Java-packages via org.atteo.classindex.processor.ClassIndexProcessor.indexPackages(String...) the processor generates jaxb.index files. Unlike the referenced jaxb-documentation

Fully qualified class names are not allowed. ...

the processor generates a fqcn for all classes in the package.
e.g. for package org.custom the jaxb.index-file contains class items like org.custom.Foobar instead of a simple relative classname Foobar.
While accessing the classNames via ClassIndex.getPackageClassesNames(String) the API returns double-package classnames like org.custom.org.custom.Foobar.
Using ClassIndex.getPackageClasses(String) seems to work. But I suppose that there is a bug writing and accessing the package jaxb.index-file fqcn-entries.

Note: Package-indexing by IndexSubclasses-annotations in package-info.java-files works fine as estimated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant