| Summary: | Support for @Generated Annotation | ||
|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | Johannes Utzig <jutzig.dev> |
| Component: | Tools | Assignee: | Ed Merks <Ed.Merks> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | sbouchet |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Johannes Utzig
Which things should all be marked this way? Everywhere we have an @generated? Does this marker on a class or interface imply anything about the contents being exclusively generated? I.e., can a @Generated interface contain things that aren't generated? (In reply to comment #1) > Which things should all be marked this way? Everywhere we have an @generated? I would think so, yes. In regard to your question about the class/interface header, I would say at least members and methods. > Does this marker on a class or interface imply anything about the contents > being exclusively generated? I.e., can a @Generated interface contain things > that aren't generated? A very good question indeed. Unfortunately, this is not clearly mentioned in the API-Doc, which makes it likely that different tools will interpret an @Generated on an interface/class differently. Some might just dismiss violations on the class declaration, while others might dismiss the class/interface completely. Since it is not stated otherwise in the API-Doc, I assume that an @Generated class/interface can contain non-generated portions, but that doesn't mean that metric tools will behave that way. I don't think there is sufficient demand for this in proportion to the effort involved. |