[jira] Commented: (MSUREFIRE-123) unable to establish my own http protocol handler for unit tests

["Markus Waserscaff (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MSUREFIRE-123?page=comments#action_82035 ] 
            
Markus Waserscaff commented on MSUREFIRE-123:
---------------------------------------------

Hi,

when forking enabled, the system properties are not set on the command line, but programmatically. 
Could this be the problem?
 I have a similar problem and I can load my custom Handler class programmatically, but it is not properly registered and thus not activated.
Is there a good reason why the system properties are set via System.setProperty() and not on the command line with -D...=...?

> 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
>          Issue Type: Bug
>    Affects Versions: 2.2
>         Environment: jse 5.0 (osx)
>            Reporter: Andy Fyfe
>             Fix For: 2.3
>
>         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