I don't quite know what its used for, but that order change can be considered incompatible, mainly cause in its current form it is (and doubles up) applying directly to the JVM that launches Mahout, but the changed form makes it into application-only arguments.
On Sun, Sep 1, 2013 at 1:05 AM, Gokhan Capan <[email protected]> wrote: > Hi Mario, > > Could you create a JIRA ticket for that, and submit your diff as a patch if > possible? > http://issues.apache.org/jira/browse/MAHOUT > > Best, > Gokhan > > > On Sat, Aug 31, 2013 at 8:56 PM, Mario Rodriguez > <[email protected]>wrote: > >> Hi everyone, >> >> It seems MAHOUT_OPTS is not getting picked up when running mahout locally >> (MAHOUT_LOCAL=true). This can be fixed by switching the order in which >> MAHOUT_OPTS is passed in bin/mahout from: >> >> exec "$JAVA" $JAVA_HEAP_MAX $MAHOUT_OPTS -classpath "$CLASSPATH" $CLASS >> "$@" >> >> to: >> >> exec "$JAVA" $JAVA_HEAP_MAX -classpath "$CLASSPATH" $CLASS "$@" >> $MAHOUT_OPTS >> >> >> I cant guarantee it wont break some other way of running it; it does not >> look like it will, but I have not tested it. >> >> Cheers, >> >> Mario >> -- Harsh J
