[jira] (MRM-837) Cannot download SNAPSHOT version

["Olivier Lamy (JIRA)" <ji...@codehaus.org>]

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

Olivier Lamy updated MRM-837:
-----------------------------

    Fix Version/s:     (was: 2.1.2)
                   2.2.0

> Cannot download SNAPSHOT version
> --------------------------------
>
>                 Key: MRM-837
>                 URL: https://jira.codehaus.org/browse/MRM-837
>             Project: Archiva
>          Issue Type: Bug
>          Components: browser
>    Affects Versions: 1.0
>         Environment: Precisely, this bugs happens in the 1.0-beta-3
> IBM Aix Unix
>            Reporter: Baptiste MATHUS
>             Fix For: 2.2.0
>
>
> Hi all,
> Our versioning is quite special, I agree : 2.1.0.beta-2.SNAPSHOT at the moment.
> The thing is: archiva accepts that this kind of artifact version be deployed, but then it doesn't allow you to download it...
> In fact, when trying to download, say, the artifactId-2.1.0.beta-2.20080613.125403-1.jar artifact, archiva throws the following exception:
> Error 404 Not Found
> The following resource does not exist: http://archiva:4000/repository//mm/socle-technique/2.1.0.beta-2.SNAPSHOT/socle-technique-2.1.0.beta-2.20080613.125403-1.jar
> org.apache.maven.archiva.repository.layout.LayoutException: Invalid path to Artifact: filename format is invalid,expected timestamp format in filename.
> 	at java.lang.Throwable.(Throwable.java:57)
> 	at java.lang.Throwable.(Throwable.java:68)
> 	at org.apache.maven.archiva.common.ArchivaException.(ArchivaException.java:38)
> 	at org.apache.maven.archiva.repository.layout.LayoutException.(LayoutException.java:39)
> 	at org.apache.maven.archiva.repository.content.DefaultPathParser.toArtifactReference(DefaultPathParser.java:134)
> 	at org.apache.maven.archiva.repository.content.RepositoryRequest.toArtifactReference(RepositoryRequest.java:121)
> 	at org.apache.maven.archiva.repository.content.RepositoryRequest.toNativePath(RepositoryRequest.java:271)
> 	at org.apache.maven.archiva.web.repository.ProxiedDavServer.process(ProxiedDavServer.java:163)
> 	at org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.service(MultiplexedWebDavServlet.java:119)
> 	at org.apache.maven.archiva.web.repository.RepositoryServlet.service(RepositoryServlet.java:167)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> 	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
> 	at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
> 	at com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:189)
> 	at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
> 	at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:39)
> 	at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
> 	at com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
> 	at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
> 	at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
> 	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
> 	at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
> 	at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
> 	at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
> 	at org.mortbay.http.HttpServer.service(HttpServer.java:909)
> 	at org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
> 	at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
> 	at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
> 	at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
> 	at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
> 	at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
> I guess the versioning we used there is quite wrong (in a release process, I think we should not suffix SNAPSHOT after a qualifier...), but the thing is: IMO, archiva should be coherent: 
> if this naming scheme is incorrect, then archiva should reject the artifact when trying to deploy it (we use the archiva webdav interface when doing mvn deploy).
> In fact, it's quite puzzling to having successfully deployed an artifact, but being unable to download it.
> Cheers.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)