[
http://jira.codehaus.org/browse/MRM-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128581#action_128581
]
james ahlborn commented on MRM-726:
-----------------------------------
Actually, it doesn't seem like even normal snapshots are being cleaned now
(with version 640793 from the 1.0.2 branch).
INFO | jvm 1 | 2008/03/25 15:34:16 | 2008-03-25 15:34:16,029 [pool-1-thread
-1] WARN org.apache.maven.archiva.consumers.DatabaseUnprocessedArtifactConsumer
:update-db-project - File scorpio-common-SNAPSHOT.pom has an invalid project mo
del [groupId:scorpio|artifactId:scorpio-common|version:1.1.5-SNAPSHOT|packaging:
null]; The model version [1.1.5-SNAPSHOT] does not match the version portion of
the filename: SNAPSHOT
> snapshot artifacts in maven1 repo with legacy timestamps not being cleaned
> --------------------------------------------------------------------------
>
> Key: MRM-726
> URL: http://jira.codehaus.org/browse/MRM-726
> Project: Archiva
> Issue Type: Bug
> Components: repository scanning
> Affects Versions: 1.0.1, 1.0.2
> Reporter: james ahlborn
> Priority: Minor
> Fix For: 1.0.x
>
>
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
