[
https://issues.apache.org/jira/browse/ACCUMULO-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966417#comment-15966417
]
Josh Elser commented on ACCUMULO-4620:
--------------------------------------
bq. Another potential issue is that this change can cause directories to stick
around as untracked files when switching between master & 1.8/1.7. This
wouldn't be the only change that is causing this but I am not sure how
comfortable developers are in using git clean.
Another thing this made me think of is the cherry-pick backport case (e.g. we
land something in master and later realize it needs to go to earlier branches).
I don't think Git is smart enough to know that it should un-nest {{modules/}},
it would just leave it in {{modules}} in the 1.7/1.8 branch. This isn't a
particularly common case (we're pretty good at applying early the first time),
but figured it was worth mentioning.
> Consolidate all Maven modules into one directory
> ------------------------------------------------
>
> Key: ACCUMULO-4620
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4620
> Project: Accumulo
> Issue Type: Improvement
> Components: build
> Reporter: Mike Walch
> Assignee: Mike Walch
> Fix For: 2.0.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Currently, Accumulo has most of its Maven modules residing in the root
> directory and some modules in a {{server}} directory. It would be great if
> all Accumulo modules were consolidate into a {{modules}} directory to put
> every module in one directory and reduce the number of directories in the
> root project directory. To simplify merges in the future, this should also be
> done for {{1.8}} and {{1.7}} branches in addition to {{master}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
