-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Preserving hand-written assertions #25
Comments
Generate the file once, move it to source control and add your assertion manually. |
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). |
Let the maven plugin generates stuff in 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. |
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. |
Hi,
if I want to add some assertions of my own (e.g. hasX), how should I do that so that they are not wiped out every time I regenerate the file?
The text was updated successfully, but these errors were encountered: