-
Notifications
You must be signed in to change notification settings - Fork 3.6k
HHH-19283: Hibernate Gradle Plugin configuration cache support #9895
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
base: main
Are you sure you want to change the base?
Conversation
shamelessly stole a fix from hibernate#9895 by @VladoKuruc to Gradle plugin test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than what I commented, this looks good to me.
|
||
this.deleteHbmFiles = getProject().getObjects().property( Boolean.class ); | ||
this.deleteHbmFiles.convention( false ); | ||
getTargetDatabaseName().convention( "H2" ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We didn't use this default before, not sure if it's a good idea to assume H2. IMO a user should explicitly have to specify the DB.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even before, I can see this.targetDatabaseName.convention("H2"
) there. Obviously, without the convention, it would have to be explicitly required. I'll do whatever you tell me.
It would be appropriate to include deprecated code cleanup in the migration guide and report plugin support in the GitHub issue Configuration Cache compatibility status
https://hibernate.atlassian.net/browse/HHH-19283
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.