[EMAIL PROTECTED] wrote:

>I've got a shell script that effectively does this for me (ant
>maven:$1)
>
Very nice solution, I was thinking of something way over-complicated !!

Starting from that, I tried to elaborate a bit more ... here is a maven 
executable
version alpha-0.0.0.0.0.0.0.0.1-dev-noarch-i386 (would that fit as a 
<dependency> ? )

----------------------------------------------------------------------
#!/bin/sh
BASEDIR=`pwd`
echo "Basedir : $BASEDIR"
echo "Maven Home : $MAVEN_HOME"

BUILDFILE="$MAVEN_HOME/build.xml"

ant -f $BUILDFILE -Dbasedir=$BASEDIR maven:$1
----------------------------------------------------------------------

For it to be usable, you still have a "triplet" of things to do :
1 - set a MAVEN_HOME property in your /etc/profile (or your personal one)
2 - copy the build.xml file from /dir/jakarta-turbine-maven/ to $MAVEN_HOME
3 - copy this script in /usr/bin (or wherever it is executable) and 
"chmod +x" it.

Now, you can have a project with a src/ dir and a project.xml file.
The script will set the basedir as the current dir and call the 
project.xml there.
(You don't need any build.xml file in your project's dir, as it will 
call the centralized one).

You have to call the targets without the "maven:" prefix (as in dion's 
script)
such as "maven compile", or "maven site".

St�phane


_________________________________________________________
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]>

Reply via email to