You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2008/01/06 18:46:57 UTC
[jira] Created: (MRM-650) Deleted metadata files still appear in
search results
Deleted metadata files still appear in search results
-----------------------------------------------------
Key: MRM-650
URL: http://jira.codehaus.org/browse/MRM-650
Project: Archiva
Issue Type: Bug
Components: indexing
Affects Versions: 1.0
Reporter: Wendy Smoak
Priority: Minor
When an entire directory tree of artifacts is removed from the repository filesystem, the metadata files still show up in search results.
To reproduce, delete any group from the repository, then click both 'Scan Repository Now' and 'Update Database Now'.
Search for the artifact again, and note that the metadata files still appear in the results.
For example, after deleting /path/to/repository/releases/commons-lang and scanning/updating, this is in the search results for commons-lang:
http://example.com/archiva/repository/releases/commons-lang/commons-lang/maven-metadata.xml
--
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
[jira] Closed: (MRM-650) Deleted metadata files still appear in
search results
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching closed MRM-650.
--------------------------------
Assignee: Maria Odea Ching
Resolution: Fixed
Fix Version/s: (was: 1.x)
1.1.1
Fix in MRM-737 also fixes this problem.
> Deleted metadata files still appear in search results
> -----------------------------------------------------
>
> Key: MRM-650
> URL: http://jira.codehaus.org/browse/MRM-650
> Project: Archiva
> Issue Type: Bug
> Components: indexing
> Affects Versions: 1.0
> Reporter: Wendy Smoak
> Assignee: Maria Odea Ching
> Priority: Minor
> Fix For: 1.1.1
>
>
> When an entire directory tree of artifacts is removed from the repository filesystem, the metadata files still show up in search results.
> To reproduce, delete any group from the repository, then click both 'Scan Repository Now' and 'Update Database Now'.
> Search for the artifact again, and note that the metadata files still appear in the results.
> For example, after deleting /path/to/repository/releases/commons-lang and scanning/updating, this is in the search results for commons-lang:
> http://example.com/archiva/repository/releases/commons-lang/commons-lang/maven-metadata.xml
--
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
[jira] Updated: (MRM-650) Deleted metadata files still appear in
search results
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-650:
---------------------------------
Fix Version/s: 1.x
> Deleted metadata files still appear in search results
> -----------------------------------------------------
>
> Key: MRM-650
> URL: http://jira.codehaus.org/browse/MRM-650
> Project: Archiva
> Issue Type: Bug
> Components: indexing
> Affects Versions: 1.0
> Reporter: Wendy Smoak
> Priority: Minor
> Fix For: 1.x
>
>
> When an entire directory tree of artifacts is removed from the repository filesystem, the metadata files still show up in search results.
> To reproduce, delete any group from the repository, then click both 'Scan Repository Now' and 'Update Database Now'.
> Search for the artifact again, and note that the metadata files still appear in the results.
> For example, after deleting /path/to/repository/releases/commons-lang and scanning/updating, this is in the search results for commons-lang:
> http://example.com/archiva/repository/releases/commons-lang/commons-lang/maven-metadata.xml
--
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
[jira] Updated: (MRM-650) Deleted metadata files still appear in
search results
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-650:
---------------------------------
Fix Version/s: (was: 1.1.1)
1.1
> Deleted metadata files still appear in search results
> -----------------------------------------------------
>
> Key: MRM-650
> URL: http://jira.codehaus.org/browse/MRM-650
> Project: Archiva
> Issue Type: Bug
> Components: indexing
> Affects Versions: 1.0
> Reporter: Wendy Smoak
> Assignee: Maria Odea Ching
> Priority: Minor
> Fix For: 1.1
>
>
> When an entire directory tree of artifacts is removed from the repository filesystem, the metadata files still show up in search results.
> To reproduce, delete any group from the repository, then click both 'Scan Repository Now' and 'Update Database Now'.
> Search for the artifact again, and note that the metadata files still appear in the results.
> For example, after deleting /path/to/repository/releases/commons-lang and scanning/updating, this is in the search results for commons-lang:
> http://example.com/archiva/repository/releases/commons-lang/commons-lang/maven-metadata.xml
--
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