-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Comments
nmihajlovski
added a commit
that referenced
this issue
Sep 5, 2012
Closed
This was referenced Aug 17, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: