[
http://jira.codehaus.org/browse/MRM-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MRM-1330:
------------------------------
Description:
- avoid query methods in the repository API (things might be happier working
against a specific store type) - consider getArtifactsBy* -> getArtifacts(
repoId, filter ); though must take care not to build another query language
- move the resolver/storage API out of the metadata API - consolidate under the
session
- make namespace use '/' instead of '.'
- unknown facets should throw an exception instead of returning null (and check
for other null returns)
- consider shorter package names for maven2 plugin and more consistent
structuring
- address things marked as "FIXME"
- review for any new instances of bloating that can be simplified
- how are we going to translate between IDs on different projects? is
"filename" mappable to other repo types?
- how could URN/URI for an artifact be utilised?
- consider artifactmetadata as a return type - is a reference all that's needed
in some cases?
- stats manager, repository merger and audit manager should use the repository
session instead of the metadata repository
- make sure code using facets has a backup if the facet is not present
was:
- avoid query methods in the repository API (things might be happier working
against a specific store type)
- move the resolver/storage API out of the metadata API
- make namespace use '/' instead of '.'
- unknown facets should throw an exception instead of returning null (and check
for other null returns)
- consider shorter package names for maven2 plugin and more consistent
structuring
- address things marked as "FIXME"
> revise repository API
> ---------------------
>
> Key: MRM-1330
> URL: http://jira.codehaus.org/browse/MRM-1330
> Project: Archiva
> Issue Type: Improvement
> Components: Design
> Affects Versions: 1.4
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.4-M1
>
>
> - avoid query methods in the repository API (things might be happier working
> against a specific store type) - consider getArtifactsBy* -> getArtifacts(
> repoId, filter ); though must take care not to build another query language
> - move the resolver/storage API out of the metadata API - consolidate under
> the session
> - make namespace use '/' instead of '.'
> - unknown facets should throw an exception instead of returning null (and
> check for other null returns)
> - consider shorter package names for maven2 plugin and more consistent
> structuring
> - address things marked as "FIXME"
> - review for any new instances of bloating that can be simplified
> - how are we going to translate between IDs on different projects? is
> "filename" mappable to other repo types?
> - how could URN/URI for an artifact be utilised?
> - consider artifactmetadata as a return type - is a reference all that's
> needed in some cases?
> - stats manager, repository merger and audit manager should use the
> repository session instead of the metadata repository
> - make sure code using facets has a backup if the facet is not present
--
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
