You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2009/11/20 03:26:55 UTC
[jira] Created: (MRM-1283) migrate Archiva's "browse" functionality
to use the metadata content repository API
migrate Archiva's "browse" functionality to use the metadata content repository API
-----------------------------------------------------------------------------------
Key: MRM-1283
URL: http://jira.codehaus.org/browse/MRM-1283
Project: Archiva
Issue Type: Improvement
Components: browser, web application
Reporter: Brett Porter
the first steps to removing direct interaction with the database - see MRM-1025 for more information.
A test of the API's implementation will be that we can utilise it directly from the webapp action classes without introducing additional business logic, and such that we can comfortably use it in the same way from the XMLRPC module. However, we also do not want presentation-related logic (or at least the organisation of the information on screen) in the repository implementation. If that is needed, a simpler replacement abstraction for RepositoryBrowsing may be appropriate.
--
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-1283) migrate Archiva's "browse"
functionality to use the metadata content repository API
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199819#action_199819 ]
Brett Porter commented on MRM-1283:
-----------------------------------
this is now in place on the branch
> migrate Archiva's "browse" functionality to use the metadata content repository API
> -----------------------------------------------------------------------------------
>
> Key: MRM-1283
> URL: http://jira.codehaus.org/browse/MRM-1283
> Project: Archiva
> Issue Type: Improvement
> Components: browser, web application
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.3
>
>
> the first steps to removing direct interaction with the database - see MRM-1025 for more information.
> A test of the API's implementation will be that we can utilise it directly from the webapp action classes without introducing additional business logic, and such that we can comfortably use it in the same way from the XMLRPC module. However, we also do not want presentation-related logic (or at least the organisation of the information on screen) in the repository implementation. If that is needed, a simpler replacement abstraction for RepositoryBrowsing may be appropriate.
--
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-1283) migrate Archiva's "browse" functionality
to use the metadata content repository API
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1283:
------------------------------
Fix Version/s: 1.3
Assignee: Brett Porter
> migrate Archiva's "browse" functionality to use the metadata content repository API
> -----------------------------------------------------------------------------------
>
> Key: MRM-1283
> URL: http://jira.codehaus.org/browse/MRM-1283
> Project: Archiva
> Issue Type: Improvement
> Components: browser, web application
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.3
>
>
> the first steps to removing direct interaction with the database - see MRM-1025 for more information.
> A test of the API's implementation will be that we can utilise it directly from the webapp action classes without introducing additional business logic, and such that we can comfortably use it in the same way from the XMLRPC module. However, we also do not want presentation-related logic (or at least the organisation of the information on screen) in the repository implementation. If that is needed, a simpler replacement abstraction for RepositoryBrowsing may be appropriate.
--
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-1283) migrate Archiva's "browse" functionality
to use the metadata content repository API
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MRM-1283.
-----------------------------
Resolution: Fixed
> migrate Archiva's "browse" functionality to use the metadata content repository API
> -----------------------------------------------------------------------------------
>
> Key: MRM-1283
> URL: http://jira.codehaus.org/browse/MRM-1283
> Project: Archiva
> Issue Type: Improvement
> Components: browser, web application
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.4
>
>
> the first steps to removing direct interaction with the database - see MRM-1025 for more information.
> A test of the API's implementation will be that we can utilise it directly from the webapp action classes without introducing additional business logic, and such that we can comfortably use it in the same way from the XMLRPC module. However, we also do not want presentation-related logic (or at least the organisation of the information on screen) in the repository implementation. If that is needed, a simpler replacement abstraction for RepositoryBrowsing may be appropriate.
--
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-1283) migrate Archiva's "browse"
functionality to use the metadata content repository API
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199851#action_199851 ]
Brett Porter commented on MRM-1283:
-----------------------------------
enhanced to import any missing information from the backing storage repository on-demand
> migrate Archiva's "browse" functionality to use the metadata content repository API
> -----------------------------------------------------------------------------------
>
> Key: MRM-1283
> URL: http://jira.codehaus.org/browse/MRM-1283
> Project: Archiva
> Issue Type: Improvement
> Components: browser, web application
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.3
>
>
> the first steps to removing direct interaction with the database - see MRM-1025 for more information.
> A test of the API's implementation will be that we can utilise it directly from the webapp action classes without introducing additional business logic, and such that we can comfortably use it in the same way from the XMLRPC module. However, we also do not want presentation-related logic (or at least the organisation of the information on screen) in the repository implementation. If that is needed, a simpler replacement abstraction for RepositoryBrowsing may be appropriate.
--
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-1283) migrate Archiva's "browse" functionality
to use the metadata content repository API
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-1283:
----------------------------------
Fix Version/s: (was: 1.3)
1.3.1
> migrate Archiva's "browse" functionality to use the metadata content repository API
> -----------------------------------------------------------------------------------
>
> Key: MRM-1283
> URL: http://jira.codehaus.org/browse/MRM-1283
> Project: Archiva
> Issue Type: Improvement
> Components: browser, web application
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.3.1
>
>
> the first steps to removing direct interaction with the database - see MRM-1025 for more information.
> A test of the API's implementation will be that we can utilise it directly from the webapp action classes without introducing additional business logic, and such that we can comfortably use it in the same way from the XMLRPC module. However, we also do not want presentation-related logic (or at least the organisation of the information on screen) in the repository implementation. If that is needed, a simpler replacement abstraction for RepositoryBrowsing may be appropriate.
--
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