You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by "Wilfried Sibla (JIRA)" <ji...@apache.org> on 2013/09/11 14:10:51 UTC
[jira] [Commented] (ACE-402) Change file repository layout and
prefs usage
[ https://issues.apache.org/jira/browse/ACE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764244#comment-13764244 ]
Wilfried Sibla commented on ACE-402:
------------------------------------
I think it would be good have this change. Because the current solution would not work after deleting (for whatever reason) the bundle cache.
And if such a action would be necessary, the repos must be recreated from the scratch.... Could be a blocker issue for us.
Changing this would have the benefit of being able to copy/move the repos to another server.
> Change file repository layout and prefs usage
> ---------------------------------------------
>
> Key: ACE-402
> URL: https://issues.apache.org/jira/browse/ACE-402
> Project: ACE
> Issue Type: Improvement
> Components: Repository
> Affects Versions: 1.0.0
> Reporter: Bram de Kruijff
>
> ACE-391 added optional configuration to the file repositories, but there are still two concerns that I would like to address which are not strictly backward compatible.
> 1) The RepositoryFactory assigns working directories based on the PID which is a hard to interpret randomly generated number. As we have logical concepts as 'customer' and 'name' for repositories I suggest to use those (in a fs safe fashion) instead.
> Eg.
> current layout : <basedir>/<pid>/<revision><extension>
> proposed layout : <basedir>/<customer>/<name>/<revision>[extension]
> 2) The RepositoryFactory uses prefs (keeping unsafe refs which is a bug) for, AFAICS, the sole purpose of guaridng uniqueness of customer/name combination. Addressing the layout as described in 1 voids the need for prefs altogether so I ould like to remove it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira