On Wed, 2003-03-12 at 10:54, [EMAIL PROTECTED] wrote: > Sure, it's been backed out. > > A few questions though: > > Jason van Zyl <[EMAIL PROTECTED]> wrote on 13/03/2003 02:32:08 AM: > > > On Wed, 2003-03-12 at 10:28, [EMAIL PROTECTED] wrote: > > > dion 2003/03/12 07:28:32 > > > > > > Modified: src/java/org/apache/maven/plugin PluginManager.java > > > Log: > > > Silently ignore the missing project.xml > > > > Sorry, but please back this out. > > > > The CLI front-end should catch the non-existance of files as that's its > > concern. Which has been fixed in the stuff I have. > > - When can we have your stuff in CVS?
Probably this weekend, I can't stop what I'm doing ATM. > - Is it mandatory to have a project.xml? I've had a few cases where > they're useless, and I've used maven just for scripting. No, you don't need a project.xml currently. The 'genapp' goal is an example of this where you can generate a skeletal app without a project.xml file. It's invalid to have no project.xml and no goals specified. This I have captured too, when this occurs help is now displayed. > -- > dIon Gillard, Multitask Consulting > Blog: http://www.freeroller.net/page/dion/Weblog > Work: http://www.multitask.com.au > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
