On Sun, 2002-07-14 at 15:52, St�phane MOR wrote: > > > > > > Log: > > o Updating the maven.xml file. Would be nice if plugins could share > > this file. > > > What about having a maven.xml in the user's dir ?
Doesn't help in this case because the maven.xml file that needs to be reused has to be the same on each target machine. Building a plugin expecting certain values in the ~/maven.xml file is not a good thing. > This would allow a user to have goals defined for all his projects. > For instance, a user could decide to send a mail a list whenever > the site is deployed. > He would have a ~/maven.xml file looking roughly like : > > <project> > <postGoal name="site:deploy"> > The mail stuff... > </postGoal> > </project> > > and then all the projects would mail something when their site is deployed . > > Thoughts ? This is reactor type stuff, though there is no reason why we can't have a ~/maven.xml though you could get some weird problems when trying to debug a problem when 5 different people are altering the way the build is occuring. > St�phane > > ___________________________________________________________ > Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran�ais ! > Yahoo! Mail : http://fr.mail.yahoo.comm > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[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: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
