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 2010/05/04 07:06:12 UTC
[jira] Created: (MRM-1381) revise webdav module in light of new
repository API
revise webdav module in light of new repository API
---------------------------------------------------
Key: MRM-1381
URL: http://jira.codehaus.org/browse/MRM-1381
Project: Archiva
Issue Type: Task
Components: WebDAV Interface
Affects Versions: 1.4
Reporter: Brett Porter
currently a lot of resolution logic and other bits and pieces occurs directly in the webdav layer.
With the new repository API in place, and after the proxy and repository grouping behaviour (linked) is migrated, the webdav should become significantly simpler.
The module should be revised for any further changes needed after that to remove the dependency on repository-layer and model. It should be a simpler interface that just provides the webdav and HTTP verbs for accessing the repository content via the resolver. All the logic belongs in the repository implementation so that it can be shared by other modules such as web and xmlrpc. This wouldn't constitute a full REST API either - that will probably more closely mirror the xmlrpc api and work with the metadata repository API as well, not just retrieving the artifacts.
This may also cause some consideration to the location of the tests - these are effectively integration tests that could be streamlined and moved into a separate module.
--
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-1381) revise webdav module in light of new
repository API
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1381:
------------------------------
Fix Version/s: Backlog
> revise webdav module in light of new repository API
> ---------------------------------------------------
>
> Key: MRM-1381
> URL: http://jira.codehaus.org/browse/MRM-1381
> Project: Archiva
> Issue Type: Task
> Components: WebDAV Interface
> Affects Versions: 1.4
> Reporter: Brett Porter
> Fix For: Backlog
>
>
> currently a lot of resolution logic and other bits and pieces occurs directly in the webdav layer.
> With the new repository API in place, and after the proxy and repository grouping behaviour (linked) is migrated, the webdav should become significantly simpler.
> The module should be revised for any further changes needed after that to remove the dependency on repository-layer and model. It should be a simpler interface that just provides the webdav and HTTP verbs for accessing the repository content via the resolver. All the logic belongs in the repository implementation so that it can be shared by other modules such as web and xmlrpc. This wouldn't constitute a full REST API either - that will probably more closely mirror the xmlrpc api and work with the metadata repository API as well, not just retrieving the artifacts.
> This may also cause some consideration to the location of the tests - these are effectively integration tests that could be streamlined and moved into a separate module.
--
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-1381) revise webdav module in light of new
repository API
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219813#action_219813 ]
Brett Porter commented on MRM-1381:
-----------------------------------
some uses of the old API to revise specifically:
- Auditable / AuditLog / AuditListener in ADR and ADRF, needs to be more event based and probably in the repository API itself
- ArchivaRepositoryMetadata, MetadataTools and related API are used in ADRF to maintain the maven metadata, which should be done in the backend storage or the group handling
- RepositoryContentFactory / ManagedRepositoryContent are used extensively to locate the content and should be migrated to the new API
- RepositoryRequest is used to construct file information and is only used here. This should be moved into the metadata spec in some way
- ArtifactReference in ADRF for deploy blocking and relocation handling
> revise webdav module in light of new repository API
> ---------------------------------------------------
>
> Key: MRM-1381
> URL: http://jira.codehaus.org/browse/MRM-1381
> Project: Archiva
> Issue Type: Task
> Components: WebDAV Interface
> Affects Versions: 1.4
> Reporter: Brett Porter
> Fix For: Backlog
>
>
> currently a lot of resolution logic and other bits and pieces occurs directly in the webdav layer.
> With the new repository API in place, and after the proxy and repository grouping behaviour (linked) is migrated, the webdav should become significantly simpler.
> The module should be revised for any further changes needed after that to remove the dependency on repository-layer and model. It should be a simpler interface that just provides the webdav and HTTP verbs for accessing the repository content via the resolver. All the logic belongs in the repository implementation so that it can be shared by other modules such as web and xmlrpc. This wouldn't constitute a full REST API either - that will probably more closely mirror the xmlrpc api and work with the metadata repository API as well, not just retrieving the artifacts.
> This may also cause some consideration to the location of the tests - these are effectively integration tests that could be streamlined and moved into a separate module.
--
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