[jira] Updated: (MRM-1312) mda5 and sha are not generated for snapshot jars

["Maria Catherine Tan (JIRA)" <ji...@codehaus.org>]

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

Maria Catherine Tan updated MRM-1312:
-------------------------------------

    Attachment: MRM-1312.patch

Added a patch for this fix with unit test.

Use the actual file, which has a timestamp + build number version, when creating a repository task for a snapshot artifact.

> mda5 and sha are not generated for snapshot jars
> ------------------------------------------------
>
>                 Key: MRM-1312
>                 URL: http://jira.codehaus.org/browse/MRM-1312
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.2.2
>            Reporter: Thorsten Scherler
>             Fix For: 1.3.1
>
>         Attachments: MRM-1312.patch
>
>
> I found a way to reproduce our problems that we have with uploading
> SNAPSHOT versions via the web-interface. 
> We tried with the following files
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.pom
> cocoon-chaperon-impl-1.0.0-SNAPSHOT.jar
> For the version we put in the web form 1.0.0-SNAPSHOT.
> The result is that archiva creates the mda5 and sha for the pom but not
> for the jar. 
> As soon we change the name of the version to 1.0.0-SNAPSHOTS. It works
> fine.
> It seems that the version *-SNAPSHOT is not working. What is the best
> approach to debug to find out what is going on and why archiva is not
> creating the mda5 and sha file.
> It sounds that the following threas may be releated to this issue:
> http://archiva.markmail.org/search/?q=Strange%20deploy%20problem#query:Strange%20deploy%20problem+page:1+mid:55mubbiv5khgk4qu+state:results
> On Mon, 2010-01-18 at 19:00 +0800, Deng Ching wrote:
> The problem seems to be in the create-missing-checksums consumer. The
> > consumer is looking for a jar with a -SNAPSHOT in the filename but the
> > actual file has a unique (timestamp + build number) snapshot version so a
> > "no such file or directory" error occurs. It works if the version is
> > -SNAPSHOTS because it was not identified as a SNAPSHOT (from the extra 'S'
> > at the end) and therefore the version wasn't converted to a unique version
> > format.
> > 

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