You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Maria Odea Ching (JIRA)" <ji...@codehaus.org> on 2008/12/08 04:50:19 UTC
[jira] Created: (MRM-1033) Changing the location of a scanned
repository results to the contents of the new location not getting indexed
Changing the location of a scanned repository results to the contents of the new location not getting indexed
-------------------------------------------------------------------------------------------------------------
Key: MRM-1033
URL: http://jira.codehaus.org/browse/MRM-1033
Project: Archiva
Issue Type: Bug
Components: indexing, repository scanning
Affects Versions: 1.2-M1, 1.1, 1.0
Reporter: Maria Odea Ching
For example, you have a repository 'test' which already has contents and is located at '../test/'. The repository has already been scanned and indexed. Now, you would like to point repository 'test' to a different repository. So you change it's location to '../another.repository/'. You wouldn't be able to index the artifacts in ../another.repository since the 'test' repository is already considered 'scanned' and the time stamp of the artifacts are older than the last scanning.
--
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-1033) Changing the location of a scanned
repository results to the contents of the new location not getting indexed
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Catherine Tan updated MRM-1033:
-------------------------------------
Attachment: MRM-1033.patch
Attached patch that will delete all stats when repository location is changed.
> Changing the location of a scanned repository results to the contents of the new location not getting indexed
> -------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1033
> URL: http://jira.codehaus.org/browse/MRM-1033
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning
> Affects Versions: 1.0, 1.1, 1.2-M1
> Reporter: Maria Odea Ching
> Fix For: 1.2.3
>
> Attachments: MRM-1033.patch
>
>
> For example, you have a repository 'test' which already has contents and is located at '../test/'. The repository has already been scanned and indexed. Now, you would like to point repository 'test' to a different repository. So you change it's location to '../another.repository/'. You wouldn't be able to index the artifacts in ../another.repository since the 'test' repository is already considered 'scanned' and the time stamp of the artifacts are older than the last scanning.
--
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] Assigned: (MRM-1033) Changing the location of a scanned
repository results to the contents of the new location not getting indexed
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching reassigned MRM-1033:
-------------------------------------
Assignee: Maria Odea Ching
> Changing the location of a scanned repository results to the contents of the new location not getting indexed
> -------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1033
> URL: http://jira.codehaus.org/browse/MRM-1033
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning
> Affects Versions: 1.0, 1.1, 1.2-M1
> Reporter: Maria Odea Ching
> Assignee: Maria Odea Ching
> Fix For: 1.2.3
>
> Attachments: MRM-1033-new.patch, MRM-1033.patch
>
>
> For example, you have a repository 'test' which already has contents and is located at '../test/'. The repository has already been scanned and indexed. Now, you would like to point repository 'test' to a different repository. So you change it's location to '../another.repository/'. You wouldn't be able to index the artifacts in ../another.repository since the 'test' repository is already considered 'scanned' and the time stamp of the artifacts are older than the last scanning.
--
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] Commented: (MRM-1033) Changing the location of a scanned
repository results to the contents of the new location not getting indexed
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194652#action_194652 ]
Brett Porter commented on MRM-1033:
-----------------------------------
that should be fine given that we have the "force scan" mode for other cases now.
> Changing the location of a scanned repository results to the contents of the new location not getting indexed
> -------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1033
> URL: http://jira.codehaus.org/browse/MRM-1033
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning
> Affects Versions: 1.0, 1.1, 1.2-M1
> Reporter: Maria Odea Ching
> Fix For: 1.2.3
>
> Attachments: MRM-1033-new.patch, MRM-1033.patch
>
>
> For example, you have a repository 'test' which already has contents and is located at '../test/'. The repository has already been scanned and indexed. Now, you would like to point repository 'test' to a different repository. So you change it's location to '../another.repository/'. You wouldn't be able to index the artifacts in ../another.repository since the 'test' repository is already considered 'scanned' and the time stamp of the artifacts are older than the last scanning.
--
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-1033) Changing the location of a scanned
repository results to the contents of the new location not getting indexed
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-1033:
----------------------------------
Fix Version/s: (was: 1.x)
1.2.3
> Changing the location of a scanned repository results to the contents of the new location not getting indexed
> -------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1033
> URL: http://jira.codehaus.org/browse/MRM-1033
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning
> Affects Versions: 1.0, 1.1, 1.2-M1
> Reporter: Maria Odea Ching
> Fix For: 1.2.3
>
>
> For example, you have a repository 'test' which already has contents and is located at '../test/'. The repository has already been scanned and indexed. Now, you would like to point repository 'test' to a different repository. So you change it's location to '../another.repository/'. You wouldn't be able to index the artifacts in ../another.repository since the 'test' repository is already considered 'scanned' and the time stamp of the artifacts are older than the last scanning.
--
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-1033) Changing the location of a scanned
repository results to the contents of the new location not getting indexed
Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Catherine Tan updated MRM-1033:
-------------------------------------
Attachment: MRM-1033-new.patch
Fixed bug found in the first patch.
Attached updated patch: MRM-1033-new.patch
> Changing the location of a scanned repository results to the contents of the new location not getting indexed
> -------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1033
> URL: http://jira.codehaus.org/browse/MRM-1033
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning
> Affects Versions: 1.0, 1.1, 1.2-M1
> Reporter: Maria Odea Ching
> Fix For: 1.2.3
>
> Attachments: MRM-1033-new.patch, MRM-1033.patch
>
>
> For example, you have a repository 'test' which already has contents and is located at '../test/'. The repository has already been scanned and indexed. Now, you would like to point repository 'test' to a different repository. So you change it's location to '../another.repository/'. You wouldn't be able to index the artifacts in ../another.repository since the 'test' repository is already considered 'scanned' and the time stamp of the artifacts are older than the last scanning.
--
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-1033) Changing the location of a scanned
repository results to the contents of the new location not getting indexed
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1033:
------------------------------
Fix Version/s: 1.x
> Changing the location of a scanned repository results to the contents of the new location not getting indexed
> -------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1033
> URL: http://jira.codehaus.org/browse/MRM-1033
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning
> Affects Versions: 1.0, 1.1, 1.2-M1
> Reporter: Maria Odea Ching
> Fix For: 1.x
>
>
> For example, you have a repository 'test' which already has contents and is located at '../test/'. The repository has already been scanned and indexed. Now, you would like to point repository 'test' to a different repository. So you change it's location to '../another.repository/'. You wouldn't be able to index the artifacts in ../another.repository since the 'test' repository is already considered 'scanned' and the time stamp of the artifacts are older than the last scanning.
--
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] Commented: (MRM-1033) Changing the location of a scanned
repository results to the contents of the new location not getting indexed
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194646#action_194646 ]
Maria Odea Ching commented on MRM-1033:
---------------------------------------
The above two are the only ways to change the repo location I think. A quick look at the patch shows that it only handles changing the location from the web UI. I don't know if there's a way to check for changes in the config file after a re-start though.
> Changing the location of a scanned repository results to the contents of the new location not getting indexed
> -------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1033
> URL: http://jira.codehaus.org/browse/MRM-1033
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning
> Affects Versions: 1.0, 1.1, 1.2-M1
> Reporter: Maria Odea Ching
> Fix For: 1.2.3
>
> Attachments: MRM-1033-new.patch, MRM-1033.patch
>
>
> For example, you have a repository 'test' which already has contents and is located at '../test/'. The repository has already been scanned and indexed. Now, you would like to point repository 'test' to a different repository. So you change it's location to '../another.repository/'. You wouldn't be able to index the artifacts in ../another.repository since the 'test' repository is already considered 'scanned' and the time stamp of the artifacts are older than the last scanning.
--
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-1033) Changing the location of a scanned
repository results to the contents of the new location not getting indexed
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching closed MRM-1033.
---------------------------------
Resolution: Fixed
Patch applied to trunk [-r882448|http://svn.apache.org/viewvc?revision=882448&view=revision]. Thanks Marica!
> Changing the location of a scanned repository results to the contents of the new location not getting indexed
> -------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1033
> URL: http://jira.codehaus.org/browse/MRM-1033
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning
> Affects Versions: 1.0, 1.1, 1.2-M1
> Reporter: Maria Odea Ching
> Assignee: Maria Odea Ching
> Fix For: 1.2.3
>
> Attachments: MRM-1033-new.patch, MRM-1033.patch
>
>
> For example, you have a repository 'test' which already has contents and is located at '../test/'. The repository has already been scanned and indexed. Now, you would like to point repository 'test' to a different repository. So you change it's location to '../another.repository/'. You wouldn't be able to index the artifacts in ../another.repository since the 'test' repository is already considered 'scanned' and the time stamp of the artifacts are older than the last scanning.
--
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] Commented: (MRM-1033) Changing the location of a scanned
repository results to the contents of the new location not getting indexed
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194557#action_194557 ]
Wendy Smoak commented on MRM-1033:
----------------------------------
What does it mean for a repository location to be changed? I can think of two ways this happens:
1. through the web UI
2. starting Archiva with a modified archiva.xml
Does the fix for this work in both of these cases? Are there any other ways to change the repo location?
> Changing the location of a scanned repository results to the contents of the new location not getting indexed
> -------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1033
> URL: http://jira.codehaus.org/browse/MRM-1033
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning
> Affects Versions: 1.0, 1.1, 1.2-M1
> Reporter: Maria Odea Ching
> Fix For: 1.2.3
>
> Attachments: MRM-1033-new.patch, MRM-1033.patch
>
>
> For example, you have a repository 'test' which already has contents and is located at '../test/'. The repository has already been scanned and indexed. Now, you would like to point repository 'test' to a different repository. So you change it's location to '../another.repository/'. You wouldn't be able to index the artifacts in ../another.repository since the 'test' repository is already considered 'scanned' and the time stamp of the artifacts are older than the last scanning.
--
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-1033) Changing the location of a scanned
repository results to the contents of the new location not getting indexed
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-1033:
----------------------------------
Fix Version/s: (was: 1.2.3)
1.3
> Changing the location of a scanned repository results to the contents of the new location not getting indexed
> -------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1033
> URL: http://jira.codehaus.org/browse/MRM-1033
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning
> Affects Versions: 1.0, 1.1, 1.2-M1
> Reporter: Maria Odea Ching
> Assignee: Maria Odea Ching
> Fix For: 1.3
>
> Attachments: MRM-1033-new.patch, MRM-1033.patch
>
>
> For example, you have a repository 'test' which already has contents and is located at '../test/'. The repository has already been scanned and indexed. Now, you would like to point repository 'test' to a different repository. So you change it's location to '../another.repository/'. You wouldn't be able to index the artifacts in ../another.repository since the 'test' repository is already considered 'scanned' and the time stamp of the artifacts are older than the last scanning.
--
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] Commented: (MRM-1033) Changing the location of a scanned
repository results to the contents of the new location not getting indexed
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157211#action_157211 ]
Maria Odea Ching commented on MRM-1033:
---------------------------------------
>From MRM-612..
Brett: "If the configuration is changed, I'd suggest all the scanning stats should be reset."
> Changing the location of a scanned repository results to the contents of the new location not getting indexed
> -------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1033
> URL: http://jira.codehaus.org/browse/MRM-1033
> Project: Archiva
> Issue Type: Bug
> Components: indexing, repository scanning
> Affects Versions: 1.0, 1.1, 1.2-M1
> Reporter: Maria Odea Ching
>
> For example, you have a repository 'test' which already has contents and is located at '../test/'. The repository has already been scanned and indexed. Now, you would like to point repository 'test' to a different repository. So you change it's location to '../another.repository/'. You wouldn't be able to index the artifacts in ../another.repository since the 'test' repository is already considered 'scanned' and the time stamp of the artifacts are older than the last scanning.
--
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