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.
I have an Annotation Processor that reports errors and warnings.
Using the native Eclipse integration, errors and warnings are shown in both the Editor and Problems view, but using the m2e-apt plugin these messages are all shown in the Error log.
This is a problem because 1) not all developers will notice annotation messages in the Error log,
2) mesages remain in Error log after they have been resolved.,
3) we want to use the m2e-apt plugin, so generated files follow Maven conventions.
I attach two screenshots showing messages from the same Annotation processor, the first using native Eclipse integration (adding Annotation Processor to FactoryPath) and the second using the m2e-apt integration with "experimental" delagation:
Thanks,
Derek
The text was updated successfully, but these errors were encountered:
It is probably possible to get the errors back from the build invocation result and turn them into Error Markers, but I'm not 100% sure.
I don't have the bandwidth to investigate right now, so I recommend you provide a PR that fixes the issue. At the very least, providing a sample project exhibiting the problem would be helpful.
I have an Annotation Processor that reports errors and warnings.
Using the native Eclipse integration, errors and warnings are shown in both the Editor and Problems view, but using the m2e-apt plugin these messages are all shown in the Error log.
This is a problem because 1) not all developers will notice annotation messages in the Error log,
2) mesages remain in Error log after they have been resolved.,
3) we want to use the m2e-apt plugin, so generated files follow Maven conventions.
I attach two screenshots showing messages from the same Annotation processor, the first using native Eclipse integration (adding Annotation Processor to FactoryPath) and the second using the m2e-apt integration with "experimental" delagation:
Thanks,
Derek
The text was updated successfully, but these errors were encountered: