Ideally, we need to move Jelly to use classworlds instead of forehead
also.
http://classworlds.werken.com/
Maven is making the move, as forehead was a only premature attempt to
solve a larger problem. classworlds solves the problem better, I believe.
Your same suggestion applies though, regarding supplying alternate
launcher config files.
-bob
On Fri, 27 Dec 2002, Mark R. Diggory wrote:
> Making jelly.bat support alternate sources for forehead.conf would good
> as well. This allows for addition of jars to the classpath when its
> unfeasable to place them into the jelly/custom directory.
>
>
> @echo off
>
> if "%FOREHEAD_CONF%"=="" set FOREHEAD_CONF=%JELLY_HOME%\bin\forehead.conf
>
> %JAVA_HOME%\bin\java -classpath
> %CLASSPATH%;%JELLY_HOME%\lib\forehead.jar
> -Dforehead.conf.file=%FOREHEAD_CONF% -Dant.home=%ANT_HOME%
> -Djelly.home=%JELLY_HOME% -Dtools.jar=%JAVA_HOME%\lib\tools.jar
> %JELLY_OPTS% com.werken.forehead.Forehead %*
>
>
> ----
> Mark
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
--
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]>
