This appears to be a problem that occurs when one build is done right after another.
MVn clean clears it up (temporarily). The problem appears to be related to the code generation for collections. Previously collections would never be built twice on the same directory. As I get time I will be messing with this to get it cleaned up. In the meantime we have a work around and I can even disable the building of the collections. Thoughts? Benson? Are you out there? Sent from my iPhone On May 16, 2012, at 7:21 PM, "Hudson (JIRA)" <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/MAHOUT-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277256#comment-13277256 > ] > > Hudson commented on MAHOUT-768: > ------------------------------- > > Integrated in Mahout-Quality #1489 (See > [https://builds.apache.org/job/Mahout-Quality/1489/]) > MAHOUT-768 - Fixed dependencies at top-level and in distribution. > (Revision 1339406) > > Result = FAILURE > tdunning : > http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1339406 > Files : > * /mahout/trunk/distribution/pom.xml > * /mahout/trunk/pom.xml > > >> Duplicated DoubleFunction in mahout and mahout-collections (mahout.math >> package). >> --------------------------------------------------------------------------------- >> >> Key: MAHOUT-768 >> URL: https://issues.apache.org/jira/browse/MAHOUT-768 >> Project: Mahout >> Issue Type: Improvement >> Components: collections, Math >> Affects Versions: 0.5, collections-1.0 >> Reporter: Dawid Weiss >> Assignee: Ted Dunning >> Priority: Minor >> Fix For: 0.7 >> >> >> DoubleFunction is duplicated in Mahout Math and Collections. There are also >> other things inside m.math.* package that are kept there to avoid circular >> dependencies... Simply removing DoubleFunction from collections is not going >> to work because it is needed for compilation (again, circular dependency >> between collections and math). I see two solutions: >> 1) extract the common definitions inside math.function.* into a separate >> module. This is a clean solution, but obviously scatters the code even >> further. >> 2) create a compilation-time, optional dependency on mahout 0.5 in >> collections, remove the entire mahout.math.* subpackage from collections and >> live with this. I don't know how Maven handles circular dependencies of this >> type: >> collections [trunk] -> [optional, required at build time] mahout.math 0.5 >> mahout.math [trunk] -> collections [trunk] >> it seems tricky and error-prone, but should also work. >> Looking for other ideas of cleaning this mess up, of course. >> Dawid > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators: > https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa > For more information on JIRA, see: http://www.atlassian.com/software/jira > >
