Batch files and script files in the bin distribution folder (bpp.bat, bpp, profile) give you a reasonable command line version. For example, in cygwin or a unixish os:
cd <bpp source distribution tree>
. bin/profile
cd <project>
bpp args...
In windows you have to create BPP_CLASSPATH and BPP_HOME environment variables and put bpp.bat in your PATH, after which bpp.bat will work. For example:
set BPP_HOME=C:\Program Files\BPP
set BPP_CLASSPATH=C:\Program Files\BPP\lib\bsh-2.0b1.jar;(whatever else you're using)
set PATH=%BPP_HOME%\bin;%PATH%
bpp args....
set BPP_CLASSPATH
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It appears that the java command line launcher ignores classpath arguments when an executable jar file is used. So this won't work:
java -cp ../lib/bsh-2.0b1.jar -jar ../bin/bpp-0.81.jar args...
Instead put BOTH in the classpath and invoke the
BPP main() directly using the old syntax:
java -cp ../lib/bsh-2.0b1.jar;../bin/bpp-0.81.jar bpp.BPP args...
Batch files and script files in the bin distribution folder (bpp.bat, bpp, profile) give you a reasonable command line version. For example, in cygwin or a unixish os:
cd <bpp source distribution tree>
. bin/profile
cd <project>
bpp args...
In windows you have to create BPP_CLASSPATH and BPP_HOME environment variables and put bpp.bat in your PATH, after which bpp.bat will work. For example:
set BPP_HOME=C:\Program Files\BPP
set BPP_CLASSPATH=C:\Program Files\BPP\lib\bsh-2.0b1.jar;(whatever else you're using)
set PATH=%BPP_HOME%\bin;%PATH%
bpp args....
set BPP_CLASSPATH