Bugzilla – Full Text Bug Listing
| Summary: | @Nonnull field should not trigger The @Nonnull field may not have been initialized when initialization happens in @PostConstruct | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | yac yac <yac> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 4.5.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |
@Nonnull field should not trigger The @Nonnull field may not have been initialized when initialization happens in @PostConstruct @ApplicationScoped class Foo { @Nonnull Bar bar; @PostConstruct public void init() { bar = new Bar(); } }