Pre-existing annotations added to fields are getting overwritten with '@Generated' annotation with the latest version

[softwarebrahma]

Hi Team,

Thank you for helping with your contributions to keep this very very useful project going strong.

Recently with the latest version when generating (with the eclipse plugin) we notice that our pre-existing annotations that we had added to the various fields are getting overwritten with '@generated' annotation.

For example:

+    @Generated(value="org.mybatis.generator.api.MyBatisGenerator", comments="Source field: xxx.xxx_info.physical_xxx_id")
+    private Integer physicalXXXId;

-  /**
-   * This field was generated by MyBatis Generator. This field corresponds to the database column xxx.xxx_info.physical_xxx_id
-   * @mbg.generated
-   */
-  @QuerySqlField(index = true)
-  @GridToStringExclude
-  private Integer physicalXXXId;

As you can see above, the two pre-existing Apache Ignite annotations (QuerySqlField & GridToStringExclude) on the field got removed.

It would be really nice to retain the existing annotations when we add this @Generated annotation on the Java model objects. Note that, the methods added are left untouched, which is good.

This is really important for us as things won't work without these annotations....currently we plan to restore the annotations with scripts post generation, but its certainly not something i am looking forward to doing for long.

Greatly appreciate if we could fix this.

Thanks
Muthu

[jeffgbutler]

This is a known issue - I wrote about it in the release notes for the 2.0.0 release.

I am working on yet another rewrite of the merger due to limitations with JavaParser, so I will revisit this and see if we can make it better.

If you could write a plugin that added these annotations when the code is generated - instead of adding them manually - it would resolve the issue.

[softwarebrahma]

This is a known issue - I wrote about it in the release notes for the 2.0.0 release.

I am working on yet another rewrite of the merger due to limitations with JavaParser, so I will revisit this and see if we can make it better.

If you could write a plugin that added these annotations when the code is generated - instead of adding them manually - it would resolve the issue.

Thanks @jeffgbutler . These are added selectively to some of the fields as needed by the feature teams manually (they are not placed on every field of the the model objects). As you note, writing a processor to restore the annotations is what i meant. But its certainly not something i am looking forward to doing as a permanent solution.

If we could revisit & address this on the rewrite as you mention, that would be ideal & would restore things.

Thanks
Muthu