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.
Do you mind filing this in JIRA please? :) Thanks, Deng On Mon, Jan 18, 2010 at 5:17 PM, Thorsten Scherler < [email protected]> wrote: > Hi all, > > 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. > > TIA for any tips. > > salu2 > -- > Thorsten Scherler <thorsten.at.apache.org> > Open Source Java <consulting, training and solutions> > > Sociedad Andaluza para el Desarrollo de la Sociedad > de la Información, S.A.U. (SADESI) > > > > >
