[hibernate-dev] To identify the version of Hibernate ORM at runtime

[Gunnar Morling]

> Or we could improve on those methods, if not actually adding some easy
to consume resource in the orm jars.

Doesn't such resource already exist, in the form of META-INF/MANIFEST.MF ->
key "Implementation-Version"?

Based on that you should be able to raise a meaningful error if the ORM
version is "too old". It doesn't help with incompatible future ORM
versions, but it should improve the experience in some cases.

2015-03-02 14:40 GMT+01:00 Sanne Grinovero <sanne at hibernate.org>:

> All,
> it looks like people get easily confused by which version of ORM is
> compatible with - for example - Hibernate Search.
>
> The expected versions are documented plenty, in readme, project
> sources, documentation and we even remind about the expectations
> frequently in blog posts.
>
> Wondering if it would be more effective to have some marker in ORM, to
> validate at least for most critical known incompatibilities at
> runtime?
>
> I realize there is no 100% foolproof in any possible solution, but
> providing a nice error message to 90% of these cases could be helpful
> to a large population already, and doesn't seem too complex for us to
> do.
>
> I guess it could be simple enough to use the existing
> org.hibernate.Version ?
> Or we could improve on those methods, if not actually adding some easy
> to consume resource in the orm jars.
>
> WDYT?
>
> Sanne
>
>  - https://hibernate.atlassian.net/browse/HSEARCH-1816
>  -
> http://stackoverflow.com/questions/28736785/org-hibernate-impl-sessionimpl-cannot-be-cast-to-org-hibernate-engine-spi-sessio/28810837#28810837
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>