Maven 2 needs to give a warning when it is being run in a Maven 1 project and there isn't a pom.xml file

I was installing Maven 2 per the Installation Instructions and after running mvn --version and seeing 2.0 I decided to "try it out" - now realize I am a build/release guy, not a java coder so I'm coming from this as a complete newbie.

So, happy that Maven 2 was installed I went over to the working directory for our Maven 1 project and typed "mvn compile" and after a couple minutes of some downloading I get the following:

[ERROR] BUILD ERROR
...
[INFO] Cannot execute mojo: resources. It requires a project, but the build is not using one.
...
[INFO] For more information, run Maven with the -e switch

ok, hmm, I'm thinking "well, I see project.xml - what the heck does it want" but I run mvn -e compile to be safe. That spews a nice stack trace (and if I was a java guy it would probably make sense) but still nothing says "hey fool - this is Maven 2 - you need a pom.xml file not that so-last-decade project.xml file!"

anywho - sorry for the long winded report - can you change the INFO message to mention pom.xml?