You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 18, 2022. It is now read-only.
Basically if I touch a file (ie edit it) that is processed by the annotation processor than the annotation processor is able to find the resources in src/main/resources (its in the classpath).
However if I do a Maven refresh configuration ("Alt-F5" = Maven -> Update Project) than the processor cannot find resources (classpath) in src/main/resources.
I presume this is something to do with what #67 was talking about with inconsistencies with incremental and full builds.
The text was updated successfully, but these errors were encountered:
I also tested with and without the maven-processor-plugin version 3.3.3
EDIT ... sorry it does work for the maven-processor-plugin if you delegate to in the project configuration as per the README but the error messages for the annotations then happen on the POM instead of the Java file (Eclipse UI).
I can't decide which behavior is better. False errors on Java files or positive hard to read errors on the POM file.
I'm not entirely sure how the above works. I know its copying the resources and I know the m2e plugin will do that but I'm not sure if it invalidates some things for incremental build or the above always causes a full build.
After a maven refresh annotation processors cannot find resources in the classpath (ie files in
src/main/resources
). Eclipse 4.12 and m2e-apt 1.5.2This might be related to:
#67
The original bug is here:
domaframework/doma#319
Basically if I touch a file (ie edit it) that is processed by the annotation processor than the annotation processor is able to find the resources in
src/main/resources
(its in the classpath).However if I do a Maven refresh configuration ("Alt-F5" = Maven -> Update Project) than the processor cannot find resources (classpath) in
src/main/resources
.I presume this is something to do with what #67 was talking about with inconsistencies with incremental and full builds.
The text was updated successfully, but these errors were encountered: