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 2009/01/02 21:53:19 UTC
[jira] Created: (MRM-1056) Option to force scanning of an
artifact/repository regardless of file dates
Option to force scanning of an artifact/repository regardless of file dates
---------------------------------------------------------------------------
Key: MRM-1056
URL: http://jira.codehaus.org/browse/MRM-1056
Project: Archiva
Issue Type: Improvement
Affects Versions: 1.1.2
Reporter: Wendy Smoak
Often I try to browse an artifact and see "Unable to find project model" even though I know the artifact is in the repository.
By default when Archiva scans a repo, it only "sees" files added since the last time the scan was run.
Currently the only way I know to re-set it is to touch the files on disk so they appear newer, or delete the database so that Archiva will start over with scanning, neither of which is ideal.
I need a way to force scanning of artifact(s) or an entire repository, regardless of the file dates.
If the 'Last Scanned' date on the Repositories page were configurable, that would allow me to set the date far back in time so that all files would appear to be "new" and it would scan everything again.
Or, some way to give it a groupId or groupId+artifactId and have it go fix its database for that subset of the repo contents.
--
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-1056) Option to force scanning of an
artifact/repository regardless of file dates
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190299#action_190299 ]
Wendy Smoak commented on MRM-1056:
----------------------------------
I brought this up again on irc and we discussed adding a checkbox next to the 'Scan Repository' button. If checked, it would mean to ignore the last scan date and scan the entire repo contents.
> Option to force scanning of an artifact/repository regardless of file dates
> ---------------------------------------------------------------------------
>
> Key: MRM-1056
> URL: http://jira.codehaus.org/browse/MRM-1056
> Project: Archiva
> Issue Type: Improvement
> Affects Versions: 1.1.2
> Reporter: Wendy Smoak
> Fix For: 1.x
>
>
> Often I try to browse an artifact and see "Unable to find project model" even though I know the artifact is in the repository.
> By default when Archiva scans a repo, it only "sees" files added since the last time the scan was run.
> Currently the only way I know to re-set it is to touch the files on disk so they appear newer, or delete the database so that Archiva will start over with scanning, neither of which is ideal.
> I need a way to force scanning of artifact(s) or an entire repository, regardless of the file dates.
> If the 'Last Scanned' date on the Repositories page were configurable, that would allow me to set the date far back in time so that all files would appear to be "new" and it would scan everything again.
> Or, some way to give it a groupId or groupId+artifactId and have it go fix its database for that subset of the repo contents.
--
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-1056) Option to force scanning of an
artifact/repository regardless of file dates
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching closed MRM-1056.
---------------------------------
Resolution: Fixed
> Option to force scanning of an artifact/repository regardless of file dates
> ---------------------------------------------------------------------------
>
> Key: MRM-1056
> URL: http://jira.codehaus.org/browse/MRM-1056
> Project: Archiva
> Issue Type: Improvement
> Affects Versions: 1.1.2
> Reporter: Wendy Smoak
> Assignee: Maria Odea Ching
> Fix For: 1.2.3
>
>
> Often I try to browse an artifact and see "Unable to find project model" even though I know the artifact is in the repository.
> By default when Archiva scans a repo, it only "sees" files added since the last time the scan was run.
> Currently the only way I know to re-set it is to touch the files on disk so they appear newer, or delete the database so that Archiva will start over with scanning, neither of which is ideal.
> I need a way to force scanning of artifact(s) or an entire repository, regardless of the file dates.
> If the 'Last Scanned' date on the Repositories page were configurable, that would allow me to set the date far back in time so that all files would appear to be "new" and it would scan everything again.
> Or, some way to give it a groupId or groupId+artifactId and have it go fix its database for that subset of the repo contents.
--
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-1056) Option to force scanning of an
artifact/repository regardless of file dates
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-1056:
----------------------------------
Fix Version/s: (was: 1.x)
1.2.3
> Option to force scanning of an artifact/repository regardless of file dates
> ---------------------------------------------------------------------------
>
> Key: MRM-1056
> URL: http://jira.codehaus.org/browse/MRM-1056
> Project: Archiva
> Issue Type: Improvement
> Affects Versions: 1.1.2
> Reporter: Wendy Smoak
> Fix For: 1.2.3
>
>
> Often I try to browse an artifact and see "Unable to find project model" even though I know the artifact is in the repository.
> By default when Archiva scans a repo, it only "sees" files added since the last time the scan was run.
> Currently the only way I know to re-set it is to touch the files on disk so they appear newer, or delete the database so that Archiva will start over with scanning, neither of which is ideal.
> I need a way to force scanning of artifact(s) or an entire repository, regardless of the file dates.
> If the 'Last Scanned' date on the Repositories page were configurable, that would allow me to set the date far back in time so that all files would appear to be "new" and it would scan everything again.
> Or, some way to give it a groupId or groupId+artifactId and have it go fix its database for that subset of the repo contents.
--
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-1056) Option to force scanning of an
artifact/repository regardless of file dates
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-1056:
----------------------------------
Fix Version/s: (was: 1.2.3)
1.3
> Option to force scanning of an artifact/repository regardless of file dates
> ---------------------------------------------------------------------------
>
> Key: MRM-1056
> URL: http://jira.codehaus.org/browse/MRM-1056
> Project: Archiva
> Issue Type: Improvement
> Affects Versions: 1.1.2
> Reporter: Wendy Smoak
> Assignee: Maria Odea Ching
> Fix For: 1.3
>
>
> Often I try to browse an artifact and see "Unable to find project model" even though I know the artifact is in the repository.
> By default when Archiva scans a repo, it only "sees" files added since the last time the scan was run.
> Currently the only way I know to re-set it is to touch the files on disk so they appear newer, or delete the database so that Archiva will start over with scanning, neither of which is ideal.
> I need a way to force scanning of artifact(s) or an entire repository, regardless of the file dates.
> If the 'Last Scanned' date on the Repositories page were configurable, that would allow me to set the date far back in time so that all files would appear to be "new" and it would scan everything again.
> Or, some way to give it a groupId or groupId+artifactId and have it go fix its database for that subset of the repo contents.
--
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-1056) Option to force scanning of an
artifact/repository regardless of file dates
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1056:
------------------------------
Fix Version/s: 1.x
> Option to force scanning of an artifact/repository regardless of file dates
> ---------------------------------------------------------------------------
>
> Key: MRM-1056
> URL: http://jira.codehaus.org/browse/MRM-1056
> Project: Archiva
> Issue Type: Improvement
> Affects Versions: 1.1.2
> Reporter: Wendy Smoak
> Fix For: 1.x
>
>
> Often I try to browse an artifact and see "Unable to find project model" even though I know the artifact is in the repository.
> By default when Archiva scans a repo, it only "sees" files added since the last time the scan was run.
> Currently the only way I know to re-set it is to touch the files on disk so they appear newer, or delete the database so that Archiva will start over with scanning, neither of which is ideal.
> I need a way to force scanning of artifact(s) or an entire repository, regardless of the file dates.
> If the 'Last Scanned' date on the Repositories page were configurable, that would allow me to set the date far back in time so that all files would appear to be "new" and it would scan everything again.
> Or, some way to give it a groupId or groupId+artifactId and have it go fix its database for that subset of the repo contents.
--
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-1056) Option to force scanning of an
artifact/repository regardless of file dates
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179465#action_179465 ]
Wendy Smoak commented on MRM-1056:
----------------------------------
On irc, Brett mentioned possibly removing the database as a way to solve this problem.
As a user, I simply want Archiva to display all of my repository content, regardless of file dates or how it got added to the repo.
> Option to force scanning of an artifact/repository regardless of file dates
> ---------------------------------------------------------------------------
>
> Key: MRM-1056
> URL: http://jira.codehaus.org/browse/MRM-1056
> Project: Archiva
> Issue Type: Improvement
> Affects Versions: 1.1.2
> Reporter: Wendy Smoak
> Fix For: 1.x
>
>
> Often I try to browse an artifact and see "Unable to find project model" even though I know the artifact is in the repository.
> By default when Archiva scans a repo, it only "sees" files added since the last time the scan was run.
> Currently the only way I know to re-set it is to touch the files on disk so they appear newer, or delete the database so that Archiva will start over with scanning, neither of which is ideal.
> I need a way to force scanning of artifact(s) or an entire repository, regardless of the file dates.
> If the 'Last Scanned' date on the Repositories page were configurable, that would allow me to set the date far back in time so that all files would appear to be "new" and it would scan everything again.
> Or, some way to give it a groupId or groupId+artifactId and have it go fix its database for that subset of the repo contents.
--
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-1056) Option to force scanning of an
artifact/repository regardless of file dates
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191426#action_191426 ]
Maria Odea Ching commented on MRM-1056:
---------------------------------------
Additional changes committed to trunk -r816545:
* added new method for creating task with scanAll flag
* added unit tests for creating tasks with different configs
> Option to force scanning of an artifact/repository regardless of file dates
> ---------------------------------------------------------------------------
>
> Key: MRM-1056
> URL: http://jira.codehaus.org/browse/MRM-1056
> Project: Archiva
> Issue Type: Improvement
> Affects Versions: 1.1.2
> Reporter: Wendy Smoak
> Assignee: Maria Odea Ching
> Fix For: 1.2.3
>
>
> Often I try to browse an artifact and see "Unable to find project model" even though I know the artifact is in the repository.
> By default when Archiva scans a repo, it only "sees" files added since the last time the scan was run.
> Currently the only way I know to re-set it is to touch the files on disk so they appear newer, or delete the database so that Archiva will start over with scanning, neither of which is ideal.
> I need a way to force scanning of artifact(s) or an entire repository, regardless of the file dates.
> If the 'Last Scanned' date on the Repositories page were configurable, that would allow me to set the date far back in time so that all files would appear to be "new" and it would scan everything again.
> Or, some way to give it a groupId or groupId+artifactId and have it go fix its database for that subset of the repo contents.
--
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-1056) Option to force scanning of an
artifact/repository regardless of file dates
Posted by "Marc Lustig (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179258#action_179258 ]
Marc Lustig commented on MRM-1056:
----------------------------------
We strongly support this proposal to add functionality for a "force scan".
Indeed users are quite annoyed by the "Unable to find project model" messages.
The option to pass a groupId/artifactId also makes sense in order to speed up the process.
> Option to force scanning of an artifact/repository regardless of file dates
> ---------------------------------------------------------------------------
>
> Key: MRM-1056
> URL: http://jira.codehaus.org/browse/MRM-1056
> Project: Archiva
> Issue Type: Improvement
> Affects Versions: 1.1.2
> Reporter: Wendy Smoak
> Fix For: 1.x
>
>
> Often I try to browse an artifact and see "Unable to find project model" even though I know the artifact is in the repository.
> By default when Archiva scans a repo, it only "sees" files added since the last time the scan was run.
> Currently the only way I know to re-set it is to touch the files on disk so they appear newer, or delete the database so that Archiva will start over with scanning, neither of which is ideal.
> I need a way to force scanning of artifact(s) or an entire repository, regardless of the file dates.
> If the 'Last Scanned' date on the Repositories page were configurable, that would allow me to set the date far back in time so that all files would appear to be "new" and it would scan everything again.
> Or, some way to give it a groupId or groupId+artifactId and have it go fix its database for that subset of the repo contents.
--
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-1056) Option to force scanning of an
artifact/repository regardless of file dates
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching reassigned MRM-1056:
-------------------------------------
Assignee: Maria Odea Ching
> Option to force scanning of an artifact/repository regardless of file dates
> ---------------------------------------------------------------------------
>
> Key: MRM-1056
> URL: http://jira.codehaus.org/browse/MRM-1056
> Project: Archiva
> Issue Type: Improvement
> Affects Versions: 1.1.2
> Reporter: Wendy Smoak
> Assignee: Maria Odea Ching
> Fix For: 1.2.3
>
>
> Often I try to browse an artifact and see "Unable to find project model" even though I know the artifact is in the repository.
> By default when Archiva scans a repo, it only "sees" files added since the last time the scan was run.
> Currently the only way I know to re-set it is to touch the files on disk so they appear newer, or delete the database so that Archiva will start over with scanning, neither of which is ideal.
> I need a way to force scanning of artifact(s) or an entire repository, regardless of the file dates.
> If the 'Last Scanned' date on the Repositories page were configurable, that would allow me to set the date far back in time so that all files would appear to be "new" and it would scan everything again.
> Or, some way to give it a groupId or groupId+artifactId and have it go fix its database for that subset of the repo contents.
--
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-1056) Option to force scanning of an
artifact/repository regardless of file dates
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191278#action_191278 ]
Maria Odea Ching commented on MRM-1056:
---------------------------------------
Fix committed to trunk -r816084 with the following changes:
* add checkbox for processing all artifacts beside Scan Repository Now button in repositories page
* scan all artifacts if flag is set
* added unit tests
> Option to force scanning of an artifact/repository regardless of file dates
> ---------------------------------------------------------------------------
>
> Key: MRM-1056
> URL: http://jira.codehaus.org/browse/MRM-1056
> Project: Archiva
> Issue Type: Improvement
> Affects Versions: 1.1.2
> Reporter: Wendy Smoak
> Assignee: Maria Odea Ching
> Fix For: 1.2.3
>
>
> Often I try to browse an artifact and see "Unable to find project model" even though I know the artifact is in the repository.
> By default when Archiva scans a repo, it only "sees" files added since the last time the scan was run.
> Currently the only way I know to re-set it is to touch the files on disk so they appear newer, or delete the database so that Archiva will start over with scanning, neither of which is ideal.
> I need a way to force scanning of artifact(s) or an entire repository, regardless of the file dates.
> If the 'Last Scanned' date on the Repositories page were configurable, that would allow me to set the date far back in time so that all files would appear to be "new" and it would scan everything again.
> Or, some way to give it a groupId or groupId+artifactId and have it go fix its database for that subset of the repo contents.
--
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-1056) Option to force scanning of an
artifact/repository regardless of file dates
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191283#action_191283 ]
Maria Odea Ching commented on MRM-1056:
---------------------------------------
Docs updated to reflect these changes in trunk -r816092.
> Option to force scanning of an artifact/repository regardless of file dates
> ---------------------------------------------------------------------------
>
> Key: MRM-1056
> URL: http://jira.codehaus.org/browse/MRM-1056
> Project: Archiva
> Issue Type: Improvement
> Affects Versions: 1.1.2
> Reporter: Wendy Smoak
> Assignee: Maria Odea Ching
> Fix For: 1.2.3
>
>
> Often I try to browse an artifact and see "Unable to find project model" even though I know the artifact is in the repository.
> By default when Archiva scans a repo, it only "sees" files added since the last time the scan was run.
> Currently the only way I know to re-set it is to touch the files on disk so they appear newer, or delete the database so that Archiva will start over with scanning, neither of which is ideal.
> I need a way to force scanning of artifact(s) or an entire repository, regardless of the file dates.
> If the 'Last Scanned' date on the Repositories page were configurable, that would allow me to set the date far back in time so that all files would appear to be "new" and it would scan everything again.
> Or, some way to give it a groupId or groupId+artifactId and have it go fix its database for that subset of the repo contents.
--
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