Thanks, frono, and thanks for all the review you've done so far. Here's a patch that has rhino in a src/jar/ directory (placing the jar still needs to be done manually). Can split this up into a sequence of patches if you'd like, but i suspect it would be easier for someone with commit access to do so when we are actually ready to commit.
svn checkout https://svn.code.sf.net/p/kolmafia/code/ kolmafia-code
cd kolmafia-code
svn patch ~/Documents/Projects/kol/old-kolmafia/javascript-v7.txt
mkdir -p src/jar
cp ~/Downloads/rhino-1.7.13.jar src/jar/
ant daily
java -jar dist/KoLmafia-20501M.jar --CLI
# js Item.get("hair spray")
We can certainly think about it but the test / JUnit environment for mafia is enough different from the one I have forgotten how to use that I'm not sure I want to reclimb the learning curve. Although there is one example of using a script in a test so...might be nice (but not show stopping, in any way) to add some of those js Item.get("hair spray") items to the tests that ant test runs.
In the interest of moving ahead, lets accept the src/jar convention. I'll create the directories and check in rhino. I'm OK with the build.xml changes in the Javascript patch so I will extract them and check them in separately from the rest of the JavaScript.
The daily task made the same jar with the directory and rhino present as it did without, using the changed build so breaking things apart doesn't seem to hurt anything or even make a difference until Javascript is added.