This is really odd. I suspect something really silly. I was able to compile without incident and the tests are going fine, though not yet completed. This is very frustrating, not just for you, but because maven is supposed to make compiling strange code easier because of stronger conventions.
Try: check java version (should be 1.6, I had to set JAVA_HOME even though my mac has 1.6 set as default) check mvn version (should be 2.09 or above) To get eclipse happy try mvn eclipse:eclipse or mvn eclipse:configure-workspace On Tue, Mar 3, 2009 at 1:40 PM, Jeff Eastman <[email protected] > wrote: > jeff-eastmans-macbook-pro:mahout-0.1 jeff$ mvn compile > [INFO] Scanning for projects... > [INFO] > ------------------------------------------------------------------------ > [ERROR] FATAL ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Error building POM (may not be this project's POM). > > > Project ID: unknown > > Reason: Could not find the model file > '/Users/jeff/Desktop/mahout-0.1/taste-web/pom.xml'. > > I think this whole switch to maven has unfortunately left me in the dust. I > would think that a RC would at least have enough instructions in it for a > reasonable person to do something useful. I still cannot figure out how to > get Eclipse to compile the trunk checkout either, so I'm dead in the water. > -- Ted Dunning, CTO DeepDyve 111 West Evelyn Ave. Ste. 202 Sunnyvale, CA 94086 www.deepdyve.com 408-773-0110 ext. 738 858-414-0013 (m) 408-773-0220 (fax)
