-
Notifications
You must be signed in to change notification settings - Fork 36
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
Ignore annotation #64
Comments
Why do you want to exclude annotations? And only annotations (like the XmlSeeAlso) in your example? |
Not sure if it makes sense to only exclude some annotations. As it's a standard annotaton we don't have plans now to remove this annotation and search for a "cleaner" way. As with other tools to improve code quality (findbugs, PMD etc) I would also appreciate if there's a way to define some exclusions in degraph cause if you don't start at the green field there are many warnings/errors when using a new tool to improve quality. If we don't have exclusions and there are too many warnings/errors on a legacy project then nobody cares or tries to remove them. As we have many entities with the mentioned annotation (only this annotations seems to make troubles so far), the output is more like spam than information. It would be helpful for us to only see "real" cycles as the XmlSeeAlso is only used for de-/serializsation and. Maybe I'm just defining the test the wrong way. I attached the very simple test project. Is there a way to define a testcase the runs without warnings without removing the annotation? |
I think I understand the issue at hand. I wouldn't include a special ignore-annotation-feature, but I have plans to make it possible to ignore dependencies (see #61). Therefore I'm closing this issue. |
It would be helpful to be able to exlude Annotation-classes in checks such as the jaxb XmlSeeAlso.
The text was updated successfully, but these errors were encountered: