Filed an issue for this: https://issues.apache.org/jira/browse/MAHOUT-768
let me know what you think. Simple removal of this class won't do the job. Dawid On Sat, Jul 23, 2011 at 8:00 PM, Ted Dunning <[email protected]> wrote: > Yes. > > On Sat, Jul 23, 2011 at 3:12 AM, Dawid Weiss > <[email protected]>wrote: > >> Yep, I see it now -- this indeed seems to be the only class left in >> Collections. Worth a patch? >> >> Dawid >> >> On Sat, Jul 23, 2011 at 12:04 PM, Sean Owen <[email protected]> wrote: >> > I believe that is the only duplication and it was an error. I think it is >> > meant to be in math, not collections. >> > >> > On Sat, Jul 23, 2011 at 11:00 AM, Dawid Weiss <[email protected]> >> wrote: >> > >> >> Hi everyone. We have decided to dump support for native matrix ops in >> >> Carrot2 (at least temporarily). Staszek will follow-up with stuff >> >> we've bumped into while moving away from Mahout 0.3 and to the 0.5, I >> >> just wanted to ask -- what was the reason for duplicating classes like >> >> DoubleFunction etc. between collections and math? In normal >> >> circumstances this is not an issue (the first class in classpath will >> >> be loaded) but in a setting where security manager is present or when >> >> somebody (ehm, like us) does trickery to merge jars, this becomes an >> >> issue. >> >> >> >> I realize any direction of dependency between mahout math and mahout >> >> collections is not convenient, but then this duplication smells bad >> >> either. >> >> >> >> Dawid >> >> >> > >> >
