On Mar 15, 2009, at 2:57 PM, Sean Owen wrote:
Ah OK. This finally succeeded after 15 minutes. I see a ton of
messages like this:
...
[WARNING] Entry:
mahout-0.2-SNAPSHOT/examples/examples/src/test/java/org/apache/
mahout/ga/watchmaker/cd/utils/RandomRuleResults.java
longer than 100 characters.
...
[INFO] mahout-0.2-SNAPSHOT/examples/mahout-examples-0.2-SNAPSHOT.jar
already added, skipping
...
I had assumed it was stuck after a minute or two and killed it in the
past. Is the time it takes normal, what others see?
The first time is often slower than the rest.
I'm looking for a 'compile' target. 'mvn compile' succeeds in core
actually, this is good. It fails in examples. Is that expected?
The examples has a dependency on the core. The core therefore needs
to be installed in the local M2 repository (~/.m2/repository). That
is what mvn install does. I don't know why a Maven multimodule build
can't figure this one out. Perhaps someone w/ better Maven chops than
I can do it. Seems to me that it should just build and install core
first. Maybe I will track down a Maven person at ApacheCon next week.
I will probably keep using my IDE for day-to-day compilation and tests
since it's faster, and as long as that works out I am cool.
I point IntelliJ at my POM and say "Import Project". Then, I use
IntelliJ's compilation and tests almost all the time. The only time I
don't is right before check in, when I want to make sure I didn't mess
anything up.
Now, I have a build.xml file for the taste-web component in place of
the pom.xml file. Everything seems to work as intended. My last
question is how to just make sure this stuff is packaged into the
build without a pom.xml file -- or does the pom.xml file have to
exist? I'm trying to avoid duplication but can put back the pom.xml
file there if it is needed.
I think we can make the taste-web work w/ the POM. What is it that
you see as lacking in there now? Try doing "mvn package". I get a
WAR file now that works, so long as I set my recommender.properties.
What I don't think we have a great solution for just yet is the
Grouplens example.
I think there are 4 basic commands that will serve most situations:
mvn compile - Compile, all dependencies must be resolvable
mvn install - compile, test and install to the local ~/.m2/repo
mvn test - Run the tests
mvn package - compile, test and package up in the appropriate format
(WAR, JAR, etc.)
HTH,
Grant
