[
https://issues.apache.org/jira/browse/MAHOUT-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991251#comment-12991251
]
Sean Owen commented on MAHOUT-608:
----------------------------------
OK that's cool to standardize on src/ if that's standard-ish. The point is
mostly to not have 3-4 "stuff" directories. Let me try again for src/
It still feels like there are many 'config' directories: (top level + src/),
mahout-eclipse-support, mahout-distribution. I don't know how much it can be
refactored but it still feels spread out.
> Collect various data directories in Mahout dir structure
> --------------------------------------------------------
>
> Key: MAHOUT-608
> URL: https://issues.apache.org/jira/browse/MAHOUT-608
> Project: Mahout
> Issue Type: Improvement
> Affects Versions: 0.4
> Reporter: Sean Owen
> Assignee: Sean Owen
> Fix For: 0.5
>
> Attachments: MAHOUT-608.patch
>
>
> The top-level project directory has collected, over time, a number of
> directories that have a generally similar purpose: to collect various config
> files, data files, and scripts. In addition toWe have, at first glance:
> bin/
> mahout
> conf/
> (various .props files)
> etc/
> build.xml (reusable Ant tasks?)
> findbugs-exclude.xml
> mahout.importorder
> mahout/
> conf/
> arff.vector.props (wrong place?)
> src/
> main/
> appended-resources/
> META-INF/
> NOTICE
> supplemental-models.xml
> site/
> site.xml
> There are a few top-level generated directories:
> input/
> ...
> output/
> ...
> testdata/
> transactions
> test.txt
> I'd like to prune whatever isn't needed anymore, and rationalize one
> directory structure as a start.
> Can anyone help by suggesting things to be removed, or a directory structure?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
