Hello,
I realized that when using Maven to build my projects, I almost always
have the reflex to type :
"maven site" instead of "ant maven:site", probably because I think that
it is more Maven than
Ant that does the job.
Should I see a psychiatrist ? ;-)
More seriously, I think it would be nice to have an executable wrapping
all the maven processes.
One could just place it where he wants, and just type "maven compile" or
"maven update".
This could be feasible because of several facts :
1 - All build.xml files accross projects are identical (same targets).
This allows to have a centralized
build.xml file with all the targets. The basedir would be set
automagically to the one in which you
type the command "maven xxx", and thus maven would search the
project.xml, sources, and stuff.
2 - As time goes, I guess that features will be added to match needs
like web application deployment,
J2EE, EJB and stuff. As these features appear, one would just have
to type "maven update", and the
centralized build file would be updated, proposing those new
features to every project you use maven
for !!!
3 - One could still use the actual build.xml file, calling "ant
maven:compile". Nothing prevents both
uses, ant if someone needs extra features, then he can modify the
build file, as usual, or even more,
submit a patch for the maven centralized build file !! ;-)
4 - The build-project.xml file in the "examples" directory could be used
to create a :
"maven create-project foo", which would produce all the directory
layout used by Maven and would
set some default properties in project and build properties.
Any thoughts ?
St�phane
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
