On 9/27/07, Wayne Fay <[EMAIL PROTECTED]> wrote: > > 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.
Have a template repository ship with the maven distro, which maven copies into the appropriate place (e.g. ~/.m2). That way the basis plugins are in place. Also, that'd make it nice for those behind firewalls. They could just take their repo after 'mvn compile' and shove it back into the maven install folder. Rezip that up and give it to your devs so they can use out of the box. > > 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. Does it validate the XML yet? As a start, just print out the results of a good XML validator... -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
