[
https://issues.apache.org/jira/browse/GEODE-8705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492172#comment-17492172
]
Patrick Johnsn commented on GEODE-8705:
---------------------------------------
By default, DUnits run without classloader isolation. This behavior can be
toggled by setting the `classloader.isolated` system property (true/false) when
launching the test(s).
> Using JBoss Modules to implement classloader isolated jar deployment
> --------------------------------------------------------------------
>
> Key: GEODE-8705
> URL: https://issues.apache.org/jira/browse/GEODE-8705
> Project: Geode
> Issue Type: New Feature
> Reporter: Udo Kohlmeyer
> Assignee: Udo Kohlmeyer
> Priority: Major
> Labels: pull-request-available
>
> Introduce Classloader isolation into Geode, to avoid the potential conflict
> of custom code dependencies, from deployed jars, and the dependencies of the
> Geode system.
> This problem became evident when Geode was still dependent on Spring
> framework 4.3 and users wanted to deploy custom jars that used Spring
> framework 5. This caused many library version conflicts.
> This problem is not limited to the usage of Spring in the system but to ANY
> dependent library that Geode and any potential custom jar would use.
> The end goal is to have a system that is Classloader isolated and allows for
> the usage of libraries of different versions within Geode without any
> conflicts.
>
> See RFC
> [https://cwiki.apache.org/confluence/display/GEODE/ClassLoader+Isolation] for
> further details
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
