[
https://issues.apache.org/jira/browse/MAHOUT-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991241#comment-12991241
]
Ted Dunning commented on MAHOUT-608:
------------------------------------
As I see it, this patch did the following:
moved conf under etc
moved a few files into etc
moved the appended resources out of src/main into etc
I don't much see the benefit here. Moving a few files into etc is an
improvement, but if conf is to be moved, it seems it should be moved into a
resources directory under src/main rather than into etc.
Similarly, moving resources out of the maven standard sort of place (under
src/main) doesn't seem a benefit.
How about an alternative where conf goes into mahout/src/main, the few files go
into mahout/etc and the appended-resources sit still?
> 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
