On 3/28/08, Attila Szegedi <[EMAIL PROTECTED]> wrote: > > Again, the conclusion I reached based on the observed symptoms was > that this is a Maven issue. Actually, it *is* a Maven issue; why would > Maven2 be allowed to break in such an ugly manner when facing a Maven1- > compliant project? Some sort of version mismatch detection and a clean > fail-fast behavior with an explanatory error message would be in > order, methinks... Would certainly reduce the kind of mailing list > traffic that you'd like to avoid :-)
Maven expects that users realize this is a M2 (or M1) project they are dealing with, and that they are using the proper M2/M1 binaries etc. Perhaps that is a poor assumption. Feel free to file this in JIRA, perhaps someone will add code to support the "when mvn runs, if pom.xml not there but project.xml is, warn user they probably should be using Maven1 binaries instead" use case you're proposing. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
