[
http://jira.codehaus.org/browse/SUREFIRE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Fabulich closed SUREFIRE-104.
---------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 2.4)
This test passes just fine with the 2.4 trunk if you set
useSystemClassLoader=true. It's annoying that this isn't the default, (making
it the default would screw up a lot of other stuff), I hope that will change in
some future version, but at least you don't have to hack Surefire to do it.
> unable to establish my own http protocol handler for unit tests
> ---------------------------------------------------------------
>
> Key: SUREFIRE-104
> URL: http://jira.codehaus.org/browse/SUREFIRE-104
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.0 (2.2 plugin)
> Environment: jse 5.0 (osx)
> Reporter: Andy Fyfe
> Attachments: protocol.zip
>
>
> In order to establish my own http protocol handler, I set the system property
> java.protocol.handler.pkgs and ensure that the tests require a fork. The
> test runs fine under maven 1.0.2, but fails under maven 2.0.4. I have tried
> both surefire 2.1.3 and 2.2, and both with the childDelegation option.
> The test sees the system property properly set, but the test's protocol
> handler is not actually used.
> The attached zip file demonstrates this problem (run "maven test" and "mvn
> test").
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
