[
https://jira.codehaus.org/browse/SUREFIRE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-293.
---------------------------------
Resolution: Won't Fix
Fix Version/s: (was: Backlog)
Since 2007 no interest in this fix. The in-process has to run in IsolatedCL,
isolating plugin's CL from your tests.
> Possibility to run test with not isolated Classloader
> -----------------------------------------------------
>
> Key: SUREFIRE-293
> URL: https://jira.codehaus.org/browse/SUREFIRE-293
> Project: Maven Surefire
> Issue Type: Improvement
> Components: classloading
> Affects Versions: 2.3
> Reporter: Piotr Tabor
> Attachments: useIsolatedClassLoaderPatch.diff
>
>
> I need a feature to run Maven's test in not isolated classloader. So I
> implemented it
> (and I attached patch to add it to maven trunk).
> I added useIsolatedClassLoader parameter (default to true), which is usefull
> only
> when forkMode is "none"/"never". If it's false - the parent classloader is
> set to the tests classloader.
> The option of not isolated classloader is important when MVN is run embaded
> in another program.
> The use case for the feature is:
> I have J2EE system with complicated Integration Tests (as Junit test
> cases).
> I used them by mvn test -Di-tests (i-tests is my profile to integration
> tests).
> Then i found, that i have to be able to test my system with using only Local
> interfaces of EJB (there are same cases that everythink is ok by "remote" and
> there are problems by local interaces - so i have to do both tests ).
> So I need to run's tests on Jboss application server. So I have written a
> service to run MVN as jboss service. But i couldn't use my test's because of
> isolated classloader.
> So please -- apply the patch to next plugin version.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
