On Mar 15, 2009, at 10:33 AM, Sean Owen wrote:
It's not that I don't understand Maven, though I am no expert. The maven build has never worked for me, even mvn compile, and it seems to be because the project somehow depends on itself in the repo? Reason: Cannot find parent: org.apache.mahout:mahout-parent for project: org.apache.mahout:mahout-core:jar:0.2-SNAPSHOT
From the top, do "mvn install". See http://cwiki.apache.org/MAHOUT/buildingmahout.html
For my purpose, it sounds like we do need an Ant build file, which I have recreated, but I suppose the build needs to work before we can think too much harder about that. Problem solved then. You can say it's convoluted -- yeah it is trying to do more than just compile and package code, and I think as a project it is important to not just say, hey, we wrote some nice code for you and here is some javadoc and best of luck to you. This is an aspect that is therefore important to me to preserve, and not something I feel like should be judged on whether Ant or Maven "thinks" that way. That's a tail wagging the dog.
Wasn't judging, just saying I had a hard time porting it b/c I didn't understand all the diff. things it was doing. Sorry if it came across that way.
To be honest the Maven build looks all over the place to me and several times bigger than the Ant scripts, and has never yet functioned for me -- I use IDE + Ant to get work done still. I sense this has been where we are stuck for months, with several people taking some valiant efforts and patching it up. Is it working at all for anyone? let's start there.
Everything works for me except the building of the actual release tarball (that works, it's just that I'm not telling it where to put things correctly).
What can I do to help? I have some cycles this week for Mahout, so just send your errors.
