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

Olivier Lamy closed MRM-1456.
-----------------------------

       Resolution: Cannot Reproduce
    Fix Version/s:     (was: 2.0.1)
         Assignee: Olivier Lamy

no more issues fix for 1.3.x except security. Please use 2.x 

> Repository Purge : Error : Invalid path to Artifact: filename format is 
> invalid,expected timestamp format in filename.
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: MRM-1456
>                 URL: https://jira.codehaus.org/browse/MRM-1456
>             Project: Archiva
>          Issue Type: Bug
>          Components: repository scanning
>    Affects Versions: 1.3.3
>            Reporter: Gayathri Muralidharan
>            Assignee: Olivier Lamy
>
> Hi,
> We were using Archiva 1.3 and the snapshots were not getting purged due to 
> the Layout exception.
> Recently we upgraded to 1.3.3 and even then the repository purge is not 
> happening due to the following error:
> Can you help us out here? Its really a tough task to clean the repository 
> without this purge option.
> The configuration and the error message are as follows:
> Configuration:
> Identifier snapshots
> Name Testing
> Directory /u/xxx/.m2/repository
> WebDAV URL http://xxx/archiva/repository/snapshots/
> Type Maven 2.x Repository
> Releases Included
> Snapshots Included
> Delete Released Snapshots
> Repository Purge By Days Older Than 1
> Repository Purge By Retention Count 2
> Scanned
> Scanning Cron 0 9 * * * ?
> Error message :2011-02-03 01:06:18,598 [pool-2-thread-1] INFO 
> org.apache.maven.archiva.consumers.core.MetadataUpdaterConsumer - Not 
> processing path that is not an artifact: 
> abc/def/SNAPSHOT/def-20110130.110618-652.jar (Invalid path to Artifact: 
> filename format is invalid,expected timestamp format in filename.)
> Thanks,
> Gayathri



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

Reply via email to