Ahh... that is a fine feature. Have you considered filing a JIRA?
(smirk) On Fri, Jul 5, 2013 at 9:06 AM, Jake Mannix <[email protected]> wrote: > We basically *do* build both kinds, but I was just referring to our helper > bin/mahout script - it would be nice if it had a simple way to launch jobs > collecting the $MAHOUT_HOME/lib/*.jar elements, and adding them directly to > a -libjars line. > > Nothing rocket science - it's easy enough to leave to the user, but making > it really easy to just take your mahout install, then drop some extra jars > in $MAHOUT_HOME/lib, and then $MAHOUT_HOME/bin/mahout ... will just pick > these up and use them in any job that they want to run. > > > On Fri, Jul 5, 2013 at 8:47 AM, Ted Dunning <[email protected]> wrote: > > > On Fri, Jul 5, 2013 at 7:19 AM, Jake Mannix <[email protected]> > wrote: > > > > > But also: Monster Jars Considered Harmful, so I should dredge up a > deploy > > > flag or something which allows us to run seamlessly with small jar + > > > libjars instead (so people [incl. me] can tack on their own jars by > > > modifying the libjar classpath instead of having to modify the build > > > itself). > > > > > > > I don't think we need a flag. We can build both kinds always (according > to > > me and nobody else just yet). > > > > > > -- > > -jake >
