You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2009/05/03 18:20:44 UTC
[jira] Created: (CONTINUUM-2214) Repository purge can't deal with
arbitrary files in local repo
Repository purge can't deal with arbitrary files in local repo
--------------------------------------------------------------
Key: CONTINUUM-2214
URL: http://jira.codehaus.org/browse/CONTINUUM-2214
Project: Continuum
Issue Type: Bug
Components: Purging
Affects Versions: 1.3.3
Environment: 1.4.0-SNAPSHOT r767365
Reporter: Wendy Smoak
Priority: Minor
I clicked the 'Purge' icon next to the DEFAULT repository purge configuration on http://localhost:9080/continuum/admin/purgeConfigList.action, and got a bunch of these errors (below) in continuum.log.
In general it is not an error to have an arbitrary file deployed alongside the artifact. This one in particular (resolver-status.properties) seems to be generated by Maven (see MNG-3421).
Until the purge logic can handle it, this should probably be a warning that the file was encountered and ignored, instead of an error and stacktrace.
2009-05-03 09:03:34,444 [pool-6-thread-1] ERROR org.apache.continuum.purge.controller.RepositoryPurgeController - Invalid path to Artifact: filename format is invalid, should start with artifactId as stated in path.: org/apache/continuum/continuum-xmlrpc-client/1.2.4-SNAPSHOT/resolver-status.properties
org.apache.continuum.purge.executor.ContinuumPurgeExecutorException: Invalid path to Artifact: filename format is invalid, should start with artifactId as stated in path.: org/apache/continuum/continuum-xmlrpc-client/1.2.4-SNAPSHOT/resolver-status.properties
at org.apache.continuum.purge.executor.DaysOldRepositoryPurgeExecutor.purge(DaysOldRepositoryPurgeExecutor.java:145)
at org.apache.continuum.purge.controller.RepositoryPurgeController.doPurge(RepositoryPurgeController.java:107)
at org.apache.continuum.purge.repository.scanner.RepositoryScannerInstance.directoryWalkStep(RepositoryScannerInstance.java:67)
at org.codehaus.plexus.util.DirectoryWalker.fireStep(DirectoryWalker.java:174)
at org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:392)
at org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:386)
at org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:386)
at org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:386)
at org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:386)
at org.codehaus.plexus.util.DirectoryWalker.scanDir(DirectoryWalker.java:386)
at org.codehaus.plexus.util.DirectoryWalker.scan(DirectoryWalker.java:345)
at org.apache.continuum.purge.repository.scanner.DefaultRepositoryScanner.scan(DefaultRepositoryScanner.java:96)
at org.apache.continuum.purge.repository.scanner.DefaultRepositoryScanner.scan(DefaultRepositoryScanner.java:50)
at org.apache.continuum.purge.task.PurgeTaskExecutor.executeTask(PurgeTaskExecutor.java:91)
at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:178)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:637)
Caused by: org.apache.maven.archiva.repository.layout.LayoutException: Invalid path to Artifact: filename format is invalid, should start with artifactId as stated in path.
at org.apache.maven.archiva.repository.content.DefaultPathParser.toArtifactReference(DefaultPathParser.java:114)
at org.apache.continuum.purge.repository.content.ManagedDefaultRepositoryContent.toArtifactReference(ManagedDefaultRepositoryContent.java:326)
at org.apache.continuum.purge.executor.DaysOldRepositoryPurgeExecutor.purge(DaysOldRepositoryPurgeExecutor.java:80)
... 19 more
--
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