You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitriy Pavlov (JIRA)" <ji...@apache.org> on 2019/03/05 15:49:00 UTC
[jira] [Updated] (IGNITE-11485) Support Automatic modules for
ignite-hibernate: Package interference with hibernate core and hibernate
for particular verion
[ https://issues.apache.org/jira/browse/IGNITE-11485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy Pavlov updated IGNITE-11485:
------------------------------------
Description:
Hibernate 5.3:
{noformat}
error: the unnamed module reads package org.apache.ignite.cache.hibernate from both ignite.hibernate.5.3 and ignite.hibernate.core
{noformat}
Hibernate 5.1:
{noformat}
error: the unnamed module reads package org.apache.ignite.cache.hibernate from both ignite.hibernate.core and ignite.hibernate.5.1
{noformat}
Hibernate 4.2:
{noformat}
error: the unnamed module reads package org.apache.ignite.cache.hibernate from both ignite.hibernate.core and ignite.hibernate.4.2
{noformat}
Probably we should be classes from hibernate-core module to org .apache.ignite.cache.hibernate.core package, but this may affect public API
Following class will be moved in case we change core package:
- HibernateAccessStrategyAdapter
- HibernateAccessStrategyFactory
- HibernateCacheProxy
- HibernateExceptionConverter
- HibernateKeyTransformer
- HibernateNonStrictAccessStrategy
- HibernateReadOnlyAccessStrategy
- HibernateReadWriteAccessStrategy
- HibernateTransactionalAccessStrategy
Alternative solution: Hibernate 5.3 is not yet released so we could move implementation for the newest version to its own subpackage. Formally it would not be a breaking change.
https://apacheignite-mix.readme.io/docs/hibernate-l2-cache
was:
Hibernate 5.3:
{noformat}
error: the unnamed module reads package org.apache.ignite.cache.hibernate from both ignite.hibernate.5.3 and ignite.hibernate.core
{noformat}
Hibernate 5.1:
{noformat}
error: the unnamed module reads package org.apache.ignite.cache.hibernate from both ignite.hibernate.core and ignite.hibernate.5.1
{noformat}
Hibernate 4.2:
{noformat}
error: the unnamed module reads package org.apache.ignite.cache.hibernate from both ignite.hibernate.core and ignite.hibernate.4.2
{noformat}
Probably we should be classes from hibernate-core module to org.apache.ignite.cache.hibernate.core package, but this may affect public API
Following class will be moved in case we change core package:
- HibernateAccessStrategyAdapter
- HibernateAccessStrategyFactory
- HibernateCacheProxy
- HibernateExceptionConverter
- HibernateKeyTransformer
- HibernateNonStrictAccessStrategy
- HibernateReadOnlyAccessStrategy
- HibernateReadWriteAccessStrategy
- HibernateTransactionalAccessStrategy
Alternative solution: Hibernate 5.3 is not yet released so we could move implementation for the newest version to its own subpackage. Formally it would not be a breaking change.
> Support Automatic modules for ignite-hibernate: Package interference with hibernate core and hibernate for particular verion
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-11485
> URL: https://issues.apache.org/jira/browse/IGNITE-11485
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Dmitriy Pavlov
> Priority: Major
>
> Hibernate 5.3:
> {noformat}
> error: the unnamed module reads package org.apache.ignite.cache.hibernate from both ignite.hibernate.5.3 and ignite.hibernate.core
> {noformat}
> Hibernate 5.1:
> {noformat}
> error: the unnamed module reads package org.apache.ignite.cache.hibernate from both ignite.hibernate.core and ignite.hibernate.5.1
> {noformat}
> Hibernate 4.2:
> {noformat}
> error: the unnamed module reads package org.apache.ignite.cache.hibernate from both ignite.hibernate.core and ignite.hibernate.4.2
> {noformat}
> Probably we should be classes from hibernate-core module to org .apache.ignite.cache.hibernate.core package, but this may affect public API
> Following class will be moved in case we change core package:
> - HibernateAccessStrategyAdapter
> - HibernateAccessStrategyFactory
> - HibernateCacheProxy
> - HibernateExceptionConverter
> - HibernateKeyTransformer
> - HibernateNonStrictAccessStrategy
> - HibernateReadOnlyAccessStrategy
> - HibernateReadWriteAccessStrategy
> - HibernateTransactionalAccessStrategy
> Alternative solution: Hibernate 5.3 is not yet released so we could move implementation for the newest version to its own subpackage. Formally it would not be a breaking change.
> https://apacheignite-mix.readme.io/docs/hibernate-l2-cache
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)