Skip to content
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

Introduce configuration property for defining jpa provider version #274

Closed
beikov opened this issue Nov 8, 2016 · 2 comments
Closed

Introduce configuration property for defining jpa provider version #274

beikov opened this issue Nov 8, 2016 · 2 comments
Assignees
Milestone

Comments

@beikov
Copy link
Member

beikov commented Nov 8, 2016

Since a fat jar deployment would make version detection impossible to some extents as has been discussed in #258, we should add a property which can be used to configure the jpa provider implementation version.

@beikov
Copy link
Member Author

beikov commented Nov 11, 2016

You can now put an implementation of HibernateVersionProvider on your classpath which provides the version via a method. This should do the trick for fat jar deployments. @jwgmeligmeyling

@jwgmeligmeyling
Copy link
Collaborator

jwgmeligmeyling commented Nov 11, 2016

Great! I'd been working on other pieces of my code as the minor Hibernate 5.2.3.Final release introduced breaking changes with setting native query parameters (they switched from 0 to 1 as start index). Pretty annoying, so I didn't have a chance to look into this issue more :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants