From: "Vincent Massol" <[EMAIL PROTECTED]> > 1/ I forgot to define lib.repo in my project and when I typed "ant > maven:site", I got an Ant error saying that the taskdef for such task > failed for some reason. Could Maven check for the existence of lib.repo > and report a nice message if it doesn't exist ?
+1 > 2/ When I run maven:xxx targets, I find that there is a *lot* of garbage > on the screen. For example, just to display some env properties > "maven:env" target, here is what appears on the screen : [snip] > Mostly it is the "project-properties" target that is generating garbage. > If I use Maven, it is because I don't want to know the internal of the > build ... (only in debug mode to see what's happening). > > One remark on naming : it would be nice I think if all Maven targets > were consistently named like "maven-xxx" > > It would be even better if there were a way of "hiding" the internal > Maven target from being printed on the screen. One solution might > involve a maven specific logger that would not print Maven internal > targets ? +1. I think this is a great idea. Maybe even allow properties in the project.properties to enable/disable the output of the internal Maven targets on a per project basis. James _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
