[ http://jira.codehaus.org/browse/MNG-1320?page=comments#action_85082 ] 
            
Kenney Westerhof commented on MNG-1320:
---------------------------------------

The handling for the 404 deletes the file from the local repository.

My fix for MNG-2712 extends the behaviour a bit: if there's a transferfailed, 
and the file does not already exist, then an empty metadata file (with defaults)
is written, to mark the error timestamp. This way, on consecutive builds,
the repo isn't checked again numerous times. 

This is because wagon doesn't always throw a ResourceDoesNotExistException
if there's a 404, it sometimes also throws it's superclass. Now errors are
marked, and the next day (or on force), an attempt is made to retrieve the 
metata
again.

> Build failed due to an empty or corrupt metadata file in the repository
> -----------------------------------------------------------------------
>
>                 Key: MNG-1320
>                 URL: http://jira.codehaus.org/browse/MNG-1320
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Adrian
>         Assigned To: John Casey
>             Fix For: 2.0.1
>
>   Original Estimate: 1 hour
>          Time Spent: 1 hour
>  Remaining Estimate: 0 minutes
>
> Build failed due to an empty or corrupt metadata file in the repository. 
> Possibly had a network error whilst downloading the metadata file. The stack 
> trace that occurred when the error was encountered was as follows.
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] 
> ----------------------------------------------------------------------------
> [INFO] Building Maven Ear plugin
> [INFO]    task-segment: [clean, install]
> [INFO] 
> ----------------------------------------------------------------------------
> [INFO] [clean:clean]
> [INFO] 
> ----------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] 
> ----------------------------------------------------------------------------
> [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not 
> exist or no valid version could be found
> [INFO] 
> ----------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 
> 'org.apache.maven.plugins:maven-resources-plugin' does not exist or no valid 
> version could be found
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1124)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1356)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:896)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:862)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:447)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137)
>       at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
>       at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
>       at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>       at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>       at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>       at java.lang.reflect.Method.invoke(Method.java:585)
>       at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>       at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>       at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>       at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: 
> The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not exist 
> or no valid version could be found
>       at 
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:225)
>       at 
> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:87)
>       at 
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:158)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1095)
>       ... 18 more
> [INFO] 
> ----------------------------------------------------------------------------
> [INFO] Total time: < 1 second
> [INFO] Finished at: Tue Oct 25 15:33:37 BST 2005
> [INFO] Final Memory: 1M/3M
> [INFO] 
> ----------------------------------------------------------------------------

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