> 1. If maven has no pom in current directory. mvn should display help > similar to this from perforce:
This sounds reasonable. Other people have requested similar functionality. We should make sure this lands in JIRA for future implementation. > 2. have "mvn help" be able to run out of the box with *no downloads* > being required. I agree, but I'm not sure how it should be implemented given that "help" is simply a plugin like all the others. So we'd need to bundle it with the zip, and then force the user to run a script to install it in the proper place etc as part of the installation. And then if they change their local repo cache location, they'll need to run it again to copy it there too. > 3. have the concept of a reverse archetype -- mvn runs and figures out > what the pom.xml should look like based on the current directory > structure. Currently the archetype concept says "*if* you make your > directory structure look like this mvn can run". Most projects do not have > this luxury. This is simply an NP-hard problem and will *never* be implemented. Every single project is (radically) different. > 4. if a pom is "broken" mvn should offer a suggestion about how to fix > it. What kind(s) of broken poms should be recoverable/detectable/fixable? Other than XML which is not well-formed, I very infrequently get broken poms personally, so I'd like to hear more suggestions. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
