No, I don't have proxy problems to run Maven. I'm happily compiling other projects and my local Maven repository is populated as required without any problems.
Usually proxy errors, or simply Maven repos not responding, translate into some 503 "Service Unavailable" messages that you can see in the log. What I get here is Maven's own "Unable to get resource from repository maven2-snapshots" which tells me that the required files are absent from the repository. There are also other errors reported like invalid pom.xml files, log4j initialization errors, missing symbols, etc. As someone said before, the build for SM trunk seems to be simply broken. I guess I'm therefore forced to get my feet wet witn SM 1.1 :( -- Pedro -- View this message in context: http://www.nabble.com/Missing-POM-files-in-src-distribution--t1444951.html#a3904376 Sent from the ServiceMix - User forum at Nabble.com.
