[ 
http://jira.codehaus.org/browse/MNG-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Bentmann closed MNG-4378.
----------------------------------

         Assignee: Benjamin Bentmann
       Resolution: Fixed
    Fix Version/s: 3.0-alpha-3

Bernd, we already [fixed a bunch of issues with 
3.0-alpha-2|http://jira.codehaus.org/browse/MNG/fixforversion/14719] so you 
might want to try out our latest SNAPSHOTs produced by our [CI 
server|https://grid.sonatype.org/ci/job/maven-3.0.x-bootstrap/jdk=1.5,label=ubuntu/ws/trunk/apache-maven/target/].

> Maven wants to create meta data files with invalid file names
> -------------------------------------------------------------
>
>                 Key: MNG-4378
>                 URL: http://jira.codehaus.org/browse/MNG-4378
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 3.0-alpha-2
>            Reporter: Bernd Vogt
>            Assignee: Benjamin Bentmann
>            Priority: Critical
>             Fix For: 3.0-alpha-3
>
>
> It seems to me that Maven 3.0-alpha-2 wants to create meta data files with 
> the URL from reprositories in the file name including the : after the 
> protocol:
> [INFO] snapshot com.odcgroup.odp:ocs-component:1.40.0-SNAPSHOT: checking for 
> updates from http://maven.oams.com/content/groups/odyssey
> [WARNING] repository metadata for: 'snapshot 
> com.odcgroup.odp:ocs-component:1.40.0-SNAPSHOT' could not be retrieved from 
> repository: http://maven.oams.com/content/groups/odyssey due to an error: 
> Specified destination directory cannot be created: 
> C:\EDS-maven-repository\com\odcgroup\odp\ocs-component\1.40.0-SNAPSHOT\maven-metadata-http:\maven.oams.com\content\groups

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