You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/08/26 05:16:50 UTC
[jira] Created: (MRM-158) automatically index proxied artifacts
automatically index proxied artifacts
-------------------------------------
Key: MRM-158
URL: http://jira.codehaus.org/browse/MRM-158
Project: Archiva
Issue Type: Improvement
Components: indexing, remote proxy
Reporter: Brett Porter
currently the proxied artifacts will only be indexed when the indexer is next run.
We should automatically index them, but some care needs to be taken:
- make sure the indexer is thread safe and won't regularly fail with a failed lock
- find the best way to hook this up by design (need to separate proxied artifacts from proxied files as this is internal to the proxy code, and don't want the indexer into the proxy code but rather in the core).
--
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-158) automatically index proxied artifacts
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-158?page=all ]
Brett Porter updated MRM-158:
-----------------------------
Fix Version/s: 1.0
> automatically index proxied artifacts
> -------------------------------------
>
> Key: MRM-158
> URL: http://jira.codehaus.org/browse/MRM-158
> Project: Archiva
> Issue Type: Improvement
> Components: indexing, remote proxy
> Reporter: Brett Porter
> Fix For: 1.0
>
>
> currently the proxied artifacts will only be indexed when the indexer is next run.
> We should automatically index them, but some care needs to be taken:
> - make sure the indexer is thread safe and won't regularly fail with a failed lock
> - find the best way to hook this up by design (need to separate proxied artifacts from proxied files as this is internal to the proxy code, and don't want the indexer into the proxy code but rather in the core).
--
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-158) automatically index proxied artifacts
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MRM-158.
----------------------------
Assignee: Brett Porter
Resolution: Duplicate
Fix Version/s: (was: 1.x)
> automatically index proxied artifacts
> -------------------------------------
>
> Key: MRM-158
> URL: http://jira.codehaus.org/browse/MRM-158
> Project: Archiva
> Issue Type: Improvement
> Components: indexing, remote proxy
> Reporter: Brett Porter
> Assignee: Brett Porter
> Priority: Critical
>
> currently the proxied artifacts will only be indexed when the indexer is next run.
> We should automatically index them, but some care needs to be taken:
> - make sure the indexer is thread safe and won't regularly fail with a failed lock
> - find the best way to hook this up by design (need to separate proxied artifacts from proxied files as this is internal to the proxy code, and don't want the indexer into the proxy code but rather in the core).
--
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