I'm only answering some questions. You can search the user list here http://www.nabble.com/Maven---Users-f178.html as well as the normal maven 2 places.
You have to do a 'mvn install' to get projects into the repo so the eclipse projects that depend on it will be able to find it. When a build fails the place to look for why varies. 1) Look at the output of mvn. It will tell WHY it failed. 2) If its a compile error, you should be able to see the compiler message there. This shouldn't be much of a problem if you fix the compile errors inside eclipse. 3) If its a junit error, you have to look inside the offending project (which you find in the mvn output by backing up until you see the "Tests" banner it prints). Look in the folder target/surefire-reports and you will see a .txt file that has informative messages about the test failure including any stack trace that junit would have printed. 4) Other kinds of errors seem to show up in the mvn output. That would be stuff like it can't connect to a remote repository or it can't find some dependency or plugin. -- Lee On 6/8/06, Andrew <[EMAIL PROTECTED]> wrote:
Hi: I have spent whole day to try maven2 inside eclipse, its frustrating, and hard to find document. Anyhow, I manage to setup all my dependency to work. But I can't setup the dependency between my projects, I put the dependent project inside <dependence> tag, but it failed to find it from repository, and eclipse could not compile it. I try to follow the tuitor(http://maven.apache.org/guides/mini/guide-ide-eclipse.html) , but it looks like the plug-in does not support flat parent-child project relationship. Also, when I use maven to compile a java code, the error msg is not useful at all, it prints stack trace from maven, but how do I know which java file at which line is wrong? Please help; thanks very much. Andrew
-- -- Lee Meador Sent from gmail. My real email address is [EMAIL PROTECTED]
