Yah, though in all honesty, we care not about classpaths.
We should ignore the user's classpath, and only set Forehead-X.jar as
the classpath when launching java. Forehead takes care of the rest.
What we need is an easy way to call this command:
$JAVACMD \
-classpath ${MAVEN_HOME}/lib/forehead-1.0-beta-1.jar \
-Dforehead.conf.file=${MAVEN_HOME}/bin/forehead.conf \
-Dtools.jar=$TOOLS_JAR \
-Dmaven.home=${MAVEN_HOME} \
$MAIN_CLASS $@
So, all we need is sanity-checking of MAVEN_HOME and TOOLS_JAR.
-bob
On Sat, 29 Jun 2002, [iso-8859-1] Ringo De Smet wrote:
> --- Ringo De Smet <[EMAIL PROTECTED]> wrote:
> > --- bob mcwhirter <[EMAIL PROTECTED]> wrote:
> > Well, I did a little bit of debugging and the problem is not in the
> > build-bootstrap.xml file, but in the Windows maven.bat file. Patch
> > attached!
>
> Forget my previous patch. It seems I hadn't noticed Nathan sent it
> already. However, in the batch files, the 'CP' environment variable is
> used to define a local classpath used by Maven to build. The use of
> 'CP' is a bit to short and actually conflicts with an environment
> variable that is already defined on my system. The attached patches for
> maven.bat and cp.bat now use 'MAVEN_CP' as environment variable.
>
> Ringo
>
> __________________________________________________
> Do You Yahoo!?
> Everything you'll ever need on one web page
> from News and Sport to Email and Music Charts
> http://uk.my.yahoo.com
--
Bob McWhirter [EMAIL PROTECTED]
The Werken Company http://werken.com/
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
