Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Can you document inJavadoc of a number of annotations that hey does not want static method?s
See original GitHub issueI work with Spring (Boot) and Eclipse. I enabled the warnings about methods that can be declared as static. The problem is Eclipse signals also methods decorated by @Autowired and other Spring decorators that does not want a static method.
I reported the problem to Eclipse, but they say they can’t trust me, it must be documented in the Javadoc of the annotations.
Can you please add this information to the annotations that doesn’t want a static method?
Thank you in advance.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Since most of the discussion of this happens on this bug at Eclipse: https://bugs.eclipse.org/bugs/show_bug.cgi?id=547451
I tend to close this issue here. Would that be fine with everybody involved?
Ok, so let me close this one here and continue the discussion on the Eclipse bug. I think having the whitelist that Stephan mentioned over there configurable would be the best choice and allow us and/or users to modify that list whenever it makes sense. We can also try to submit a PR for that whitelist with the most famous Spring annotations, maybe that is enough of an “official” thing from the Spring team. Let’s see.