On 15 September 2011 10:48, Sean Owen <sro...@gmail.com> wrote: > Hmm, I don't see this, anyone else? > You could run with -x (I think, or is it -v?) to have it show you the > dependency tree and what's pulling this in.
I did a clean and rebuild from trunk (OSX here), didn't get any problems; but I had that library in ~/.m2/ already. So - If I zap my ~/.m2/ and retry 'maven package -DskipTests' in $MAHOUT_HOME, after a while I see it was fetched: .m2/repository/jfree/jcommon .m2/repository/jfree/jcommon/1.0.12 .m2/repository/jfree/jcommon/1.0.12/_maven.repositories .m2/repository/jfree/jcommon/1.0.12/jcommon-1.0.12.jar .m2/repository/jfree/jcommon/1.0.12/jcommon-1.0.12.jar.sha1 .m2/repository/jfree/jcommon/1.0.12/jcommon-1.0.12.pom .m2/repository/jfree/jcommon/1.0.12/jcommon-1.0.12.pom.sha1 (and then builds successfully; as does cd examples; mvn package -DskipTests subsequently) If you start fresh without Maven's old ~/.m2/ does that help? Dan
