[infinispan-issues] [JBoss JIRA] (IPROTO-91) Allow SerializationContextInitializer dependencies
Nistor Adrian (Jira)
issues at jboss.org
Mon May 13 09:48:00 EDT 2019
[ https://issues.jboss.org/browse/IPROTO-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nistor Adrian resolved IPROTO-91.
---------------------------------
Fix Version/s: 4.3.0.Alpha2
Resolution: Done
Resolved by commit https://github.com/infinispan/protostream/commit/2a2c09646ad6a57b4ae51fdd964d4f71698bc0d9
> Allow SerializationContextInitializer dependencies
> --------------------------------------------------
>
> Key: IPROTO-91
> URL: https://issues.jboss.org/browse/IPROTO-91
> Project: Infinispan ProtoStream
> Issue Type: Enhancement
> Affects Versions: 4.3.0.Alpha1
> Reporter: Ryan Emerson
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 4.3.0.Alpha2
>
>
> In order to avoid split-packages across multiple maven modules and the resulting jars, it's necessary for Protostream to provide a mechanism for {{SerializationContextInitializer}} implementations in one module to depend on those defined in dependent modules.
> For example, the {{org.infinispan.commons.io.ByteBufferImpl}} class is defined in the Infinispan commons module, but is required by several annotated Pojos in the core module. In order for the core module to compile, it is necessary for {{ByteBufferImpl.class}} to be added to the {{classes}} field in the core modules {{AutoProtoSchemaBuilder}} annotation with {{autoImportClasses == false}} or for {{autoImportClasses == true}}. Either way, this results in {{org.infinispan.commons.io.ByteBufferImp$_Marshaller.class}} being added to the core jar.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the infinispan-issues
mailing list