Preserving hand-written assertions about assertj-assertions-generator-maven-plugin HOT 4 CLOSED

Generate the file once, move it to source control and add your assertion manually.
You can generate the assertions again in the future if the domain classes change and transfer any new assertions method to the Assert class you have moved in source control.

from assertj-assertions-generator-maven-plugin.

So manual merging... when the file is in SC, it is readonly and the maven plugin fails in that case. Would it be possible to add a setting to just continue when the target file is readonly instead of failing? That would allow me to still automatically create the Assertions file (I don't want to merge that one manually).

from assertj-assertions-generator-maven-plugin.

Let the maven plugin generates stuff in target directory, open the generated Assert file and copy the new assertions in the Assert class in source control.

This plugin was meant to quickly start using custom assertions but I always had in mind that once generated they should be moved to source control and enriched with hand written assertions that the generator can't create.

from assertj-assertions-generator-maven-plugin.

The work to keep manually written assertions requires a huge change in the assertion generator as it was not designed with that purpose in mind. I'm closing this issue for that reason, I like the idea though.
Moreover as custom assertions templates are going to be supported, users will be able to generate richer assertions, it does not completely address this issue but should improve things.

from assertj-assertions-generator-maven-plugin.