[ 
https://jira.codehaus.org/browse/MDEP-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MDEP-353.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 2.6
         Assignee: Robert Scholte

While going through the open issues I noticed this one, and it even includes a 
patch.
Meanwhile I've already fixed this issue in 
[r1396221|http://svn.apache.org/viewvc?rev=1396221&view=rev]
If only I had seen this ticket before...
Thanks!

                
> Unit tests fail on Windows
> --------------------------
>
>                 Key: MDEP-353
>                 URL: https://jira.codehaus.org/browse/MDEP-353
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Bug
>    Affects Versions: 2.5
>         Environment: Windows 7, x86_64
>            Reporter: Art O Cathain
>            Assignee: Robert Scholte
>            Priority: Minor
>             Fix For: 2.6
>
>         Attachments: build-windows.patch
>
>
> The TestGetMojo unit test of this plugin fail for me on Windows with 
> org.apache.maven.plugin.MojoExecutionException: Couldn't download artifact: 
> Unable to download the artifact from any repository
> The root cause is an IOException at AbstractWagon line 203:
> java.io.FileNotFoundException: 
> [snip]maven-dependency-plugin\target\unit-tests\markers\org.apache.maven:maven-model:jar:2.0.9.tmp
>  (The filename, directory name, or volume label syntax is incorrect)
> The StubArtifactRepository is trying to create a file with a colon in it, and 
> Windows doesn't like that.
> See attached patch for a possible fix. It might be better to fix 
> StubArtifactRepository in the maven-plugin-testing-harness but I'm a little 
> nervous of breaking other plugin builds.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to