[ http://jira.codehaus.org/browse/MSUREFIRE-148?page=comments#action_76940 
] 
            
William Ferguson commented on MSUREFIRE-148:
--------------------------------------------

I presume that the appropriate work around for this is to move your local 
repository to somewhere that doesn't have spaces in its path and to change the 
<localRepository> attributes in settings.xml to point to the new Repository 
location? That seems to work, but being a Maven newbie I'm not 100% confident.

Twoother questions
1) Whats the latest release of the surefire plugin? 2.0 is what is being 
downloaded to my local repository, but I see references to 2.1 and 2.2 on the 
mailing list, but I can't seem to get them to download :

  [INFO] Failed to resolve artifact.

  GroupId: org.apache.maven.surefire
  ArtifactId: surefire
  Version: 2.2

  Reason: Unable to download the artifact from any repository

    org.apache.maven.surefire:surefire:pom:2.2

  from the specified remote repositories:
    central (http://repo1.maven.org/maven2)

2) Whats the estimate for a release of 2.3?

> SurefireBooter can initialize classloader with badly formed URLs
> ----------------------------------------------------------------
>
>                 Key: MSUREFIRE-148
>                 URL: http://jira.codehaus.org/browse/MSUREFIRE-148
>             Project: Maven 2.x Surefire Plugin
>          Issue Type: Bug
>            Reporter: Jeremy Boynes
>         Assigned To: Brett Porter
>             Fix For: 2.3
>
>         Attachments: urlEncode.patch
>
>
> In SurefireBooter.createClassLoader() the path is converted to a URL using
>                 File f = new File( url );
>                 urls.add( f.toURL() );
> File.toURL does not perform URL encoding so the resulting URL may contain 
> invalid characters. This is an issue on Windows machines where the default 
> maven repository is in "C:\Documents and Settings\user\.m2\..." (the filename 
> contains spaces). If a test accesses a resource that is loaded from a 
> dependency jar then the URL returned to that test is malformed.
> With JDK 1.4 this can be fixed using
>                 urls.add( f.toURI().toURL() );
> as toURI() does encode the path. If surefire still needs to run under pre-1.4 
> JVMs this would need to be explicitly encoded. I'm willing to supply a patch 
> for that if wanted.

-- 
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

        

Reply via email to