archiva-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james ahlborn (JIRA)" <>
Subject [jira] Commented: (MRM-726) snapshot artifacts in maven1 repo with legacy timestamps not being cleaned
Date Mon, 03 Mar 2008 21:05:28 GMT


james ahlborn commented on MRM-726:

I'm not sure if this problem is related to this exception I'm getting in the logs:

archiva.log.2008-03-01:46980222 [pool-1-thread-1] WARN  org.apache.maven.archiva.consumers.DatabaseUnprocessedArtifactConsumer:update-db-project
 - File hmsCommon-jwrap-20070308.050344.pom has an invalid project model [groupId:null|artifactId:null|version:1.0.3|packaging:null]:
The model artifactId [null] does not match the artifactId portion of the filename: hmsCommon-jwrap

> snapshot artifacts in maven1 repo with legacy timestamps not being cleaned
> --------------------------------------------------------------------------
>                 Key: MRM-726
>                 URL:
>             Project: Archiva
>          Issue Type: Bug
>          Components: repository scanning
>    Affects Versions: 1.0.1, 1.0.2
>            Reporter: james ahlborn
>            Priority: Minor
> we have artifacts in our maven1 repository which are fairly old (one of the reasons we
wanted to use archiva, to clean up the crud!).  however, it appears that some of the snapshots
are not being cleaned up.  my guess is that it is due to an unrecognized timestamp format:
> For an artifact with artifactId "hmsCommon-jwrap", we have snapshots which look like:
> hmsCommon-jwrap-20070308.050344.jar
> // unit test
> public void testLegacyVersion() {
>   assertTrue(VersionUtil.isSnapshot("20070308.050344"));
> }

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message