AFAIK a dot component in a path is still a valid URL so IMO the bug is on the server side. While it is probably a good idea for maven to normalize the path before the PUT, that's no reason to throw a 500 (internal server error...)

Cheers,
-Lukas


Dennis Lundberg wrote:
Hi

After looking at the log over at the google code issue tracker, I think
this bug is in Wagon.

Uploading: ./css/maven-base.css to
https://m4enterprise.googlecode.com/svn/site

We should probably normalize the path before doing a PUT. On the other
hand, it might be the the Site Plugin that is feeding it the wrong path.
Please file an issue in JIRA for either of the projects so that we can
track it properly.


On 2010-12-15 23:24, Marcin Kuthan wrote:
I configured extension explicitly:

<extension>
        <artifactId>wagon-webdav-jackrabbit</artifactId>
     <groupId>org.apache.maven.wagon</groupId>
     <version>1.0-beta-7</version>
</extension>

Exactly the same URL with '/./' and stack trace:

Caused by: org.apache.maven.wagon.TransferFailedException: Failed to
transfer file: 
https://m4enterprise.googlecode.com/svn/site/./css/maven-base.css.
Return code is: 500
         at 
org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:368)
         at 
org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:280)
         at 
org.apache.maven.wagon.providers.webdav.WebDavWagon.putDirectory(WebDavWagon.java:188)
         at 
org.apache.maven.wagon.providers.webdav.WebDavWagon.putDirectory(WebDavWagon.java:182)
         at 
org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:257)
         ... 21 more



On 15 December 2010 22:46, Dennis Lundberg<[email protected]>  wrote:
Hi

Which version of the WebDAV Wagon are you using? Please try the latest
1.0-beta-7 if you aren't using it.

On 2010-12-15 21:59, Marcin Kuthan wrote:
Hi,

I configured my project to use Wagon WebDAV provider to deploy project
site. In general it works as I expected but it fails if the site is
deployed on googlecode.

Transfer error: org.apache.maven.wagon.TransferFailedException: Failed
to transfer file:
https://m4enterprise.googlecode.com/svn/site/./css/maven-base.css.
Return code is: 500
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:deploy
(default-deploy) on project corporate-pom: Error uploading site:
Failed to transfer file:
https://m4enterprise.googlecode.com/svn/site/./css/maven-base.css.
Return code is: 500 ->  [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:deploy
(default-deploy) on project corporate-pom: Error uploading site
       at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:203)
       at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
       at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
       at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
       at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
       at 
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
       at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
       at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
       at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
       at org.apache.maven.cli.MavenCli.execute(MavenCli.java:451)
       at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:188)
       at org.apache.maven.cli.MavenCli.main(MavenCli.java:134)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
       at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
       at java.lang.reflect.Method.invoke(Method.java:616)
       at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
       at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
       at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
       at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error uploading site
       at 
org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:271)
       at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
       at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195)
       ... 19 more
Caused by: org.apache.maven.wagon.TransferFailedException: Failed to
transfer file: 
https://m4enterprise.googlecode.com/svn/site/./css/maven-base.css.
Return code is: 500
       at 
org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:368)
       at 
org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:280)
       at 
org.apache.maven.wagon.providers.webdav.WebDavWagon.putDirectory(WebDavWagon.java:188)
       at 
org.apache.maven.wagon.providers.webdav.WebDavWagon.putDirectory(WebDavWagon.java:182)
       at 
org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:257)
       ... 21 more


I filled an issue in googlecode bug tracker
(http://code.google.com/p/support/issues/detail?id=4786). There is a
suspicion that '/./' part of URL is an error cause. Do you know how to
configure site plugin (or wagon) to avoid '/./' in the URL during site
deployment?

Thanks,
Marcin

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]




--
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to