I use it live from the top as well (but don't particularly care where it is.
I think that we are agreed that it has to survive into the source distribution (and the binary distribution as well, of course). On Mon, Oct 25, 2010 at 5:20 PM, Drew Farris <[email protected]> wrote: > I do use it live at the top of the build tree, and it is likely anyone > else that's running from trunk does as well. For example, > examples/bin/build-reuters.sh script expects it to be there. > > What was the reason for moving the distribution assembly to a > sub-module in the first place? I can't recall the motivation there. > > On Mon, Oct 25, 2010 at 8:09 PM, Benson Margulies <[email protected]> > wrote: > > Well, making it live at the top of the source tree is not working. Can > > you explain why that makes a big difference? Are you actually using > > the mahout script, live, in the build tree? If so, I need to find a > > different solution to the problem at hand. > > > > On Mon, Oct 25, 2010 at 8:02 PM, Drew Farris <[email protected]> > wrote: > >> No, the bin directory should live at the top level of the source tree > >> On Oct 25, 2010 7:55 PM, "Benson Margulies" <[email protected]> > wrote: > >>> Hang on everyone. Jeff is trying to prove that you can build the > >>> distro, bin and all, from the src tarball. > >>> > >>> He's right! Something's wrong. No bin directory If I fetch from svn at > >>> the mahout-0.4 tag and build, I get a bin. If I grab from the repo, I > >>> do not get a bin. > >>> > >>> I know what the problem is. Since the mahout shell script lives > >>> outside any of the maven projects, it is not swept into the source > >>> archive all all. > >>> > >>> So, I VOTE -1, and I will fix this. > >>> > >>> I owe Jeff a giant apology and a thank-you for finding this. > >>> > >>> The fix is to move that bin directory. I'm going to do that right now. > >> > > >
