When using eclipse without maven-processor-plugin, one always gets the error "... does not contain suitable methods...".
Using maven-processor-plugin in eclipse makes errors only appear in the error log, not in the markers view where all compilation errors go into.
Thus, the errors are not marked in the code and one does not notice the error at all most of the time.
This makes the maven-processor-plugin unusable for us.
For this reason it'd be great if you could incorporate the fix although you obviously have no need for it.
If you prefer a wrapper for the Types class to encapsulate the compatibility logic I'd change that and create another pull request.
hpehl
commented
8 years ago
When using eclipse without maven-processor-plugin, one always gets the error "... does not contain suitable methods...". Using maven-processor-plugin in eclipse makes errors only appear in the error log, not in the markers view where all compilation errors go into. Thus, the errors are not marked in the code and one does not notice the error at all most of the time. This makes the maven-processor-plugin unusable for us.
For this reason it'd be great if you could incorporate the fix although you obviously have no need for it.
If you prefer a wrapper for the Types class to encapsulate the compatibility logic I'd change that and create another pull request.