[
https://issues.apache.org/jira/browse/ACE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630090#comment-13630090
]
Marcel Offermans commented on ACE-316:
--------------------------------------
Yes, our repository should be able to support different types of artifacts. In
that sense it should not only implement but maybe also extend the specification
(unless that is already supported). For each file type, a naming convention
should probably be "invented" (either something default, or something that can
be plugged in for each file type).
Refactoring the REST API is also covered in ACE-317 btw, so feel free to take
that issue on as well.
Maybe our store should start with a folder for each file type, so
store/bundle/org/apache/commons... etc. for bundles and autoconf/.... for our
configuration files, etc.
> Layout the OBR filesystem differently.
> --------------------------------------
>
> Key: ACE-316
> URL: https://issues.apache.org/jira/browse/ACE-316
> Project: ACE
> Issue Type: Question
> Components: OBR
> Reporter: Marcel Offermans
> Assignee: Bram de Kruijff
>
> Currently, the OBR uses a single folder to store all artifacts. That does not
> scale too well as OS specific directory limits might interfere. We should
> implement a more hierarchical storage format, such as: <BSN>/<version> or
> even one where each part of the BSN becomes a folder.
--
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
