[ http://jira.codehaus.org/browse/MSUREFIRE-123?page=comments#action_67226 ]
Andy Fyfe commented on MSUREFIRE-123: ------------------------------------- I've tried this now also on solaris and linux. In the case of our solaris machine, an attempt to access http://localhost is denied, and the test fails with the following error: $ cat target/surefire-reports/test.HandlerTest.txt ------------------------------------------------------------------------------- Test set: test.HandlerTest ------------------------------------------------------------------------------- Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.707 sec <<< FAILURE! testHandelr(test.HandlerTest) Time elapsed: 0.277 sec <<< FAILURE! junit.framework.AssertionFailedError: expected:<200> but was:<403> In the case of our linux machine, it's a 502 error instead of a 403 from the web server, so the test report is essentially the same. > unable to establish my own http protocol handler for unit tests > --------------------------------------------------------------- > > Key: MSUREFIRE-123 > URL: http://jira.codehaus.org/browse/MSUREFIRE-123 > Project: Maven 2.x Surefire Plugin > Type: Bug > Versions: 2.2 > 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
