> > I'm not sure we have to introduce a replacement for @Generated, i maybe > wrong but the retention of this annotation is the source, so it's an > indication for the developer more than anything else, so each framework can > come with its own annotation and in my opinion, it will make the > dependencies more clear. >
It's an indication for the developer, for the users of the library using it and for tools analyzing the source code. The whole point of it was to have a common annotation used by all code generators so that tools could rely on it. See my example about error-prone in a previous email. I don't see how having a gazillion of @Generated annotations - one per project - would help and would make it useful. See the introduction of the JSR, I can't paraphrase it better: it was the whole purpose of it. -- Guillaume
