Rebuilt with all-new .m2/. It has something to do with easymock, and Maven gets the back-rev 1.0.12 instead of the specified 1.0.16.
If this is the worst "RPM hell" that Maven has to offer, that's cool. Never mind. On Thu, Sep 15, 2011 at 2:52 AM, Dan Brickley <[email protected]> wrote: > On 15 September 2011 10:48, Sean Owen <[email protected]> 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 > -- Lance Norskog [email protected]
