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

The "field sorter" work-around doesn't work for classes outside the sources input/output directory. #55

Closed
nmihajlovski opened this issue Sep 4, 2012 · 0 comments

Comments

@nmihajlovski
Copy link
Contributor

The "field sorter" work-around needs to find the Java source files, to be able to read the field order from there.
So far, the generated sources folder was configured to be the same as the originating sources folder (e.g. "src/main/java" or "src") and it was used to search the Java source file for the model. But if the model class is in other package (e.g. "src/test/java", the field sorter searches for the model Java file in the configured output folder (e.g. "src/main/java"), so it cannot find it.

Thus, to support additional source folders, the annotation processor needs additional configuration, e.g. path="src/test/java".
When such feature is implemented, it will give flexibility to specify more source paths, e.g. path="src/main/java:src/test/java", giving additional flexibility to specify any input folders for the "model" sources and any output folder for the generated sources.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant