The other options that occurs to me is to give language authors a sort of "developer account" that allows them to pull their own languages, but not others.
apache-commons-el.noarch : The Apache Commons Extension Language
apache-commons-io.noarch : Utilities to assist with developing IO functionality
apache-commons-cli.noarch : Command Line Interface Library for Java
apache-commons-csv.noarch : Utilities to assist with handling of CSV files
apache-commons-jci.noarch : Commons Java Compiler Interface
apache-commons-jcs.noarch : Apache Commons Java Caching System
apache-commons-net.noarch : Internet protocol suite Java library
apache-commons-vfs.noarch : Commons Virtual File System
Do you have any code that should work with Apache Commons but doesn't? That way, I can do some troubleshooting.
Looks like the classpath I had works just fine. Your code doesn't seem to work though. import org.apache.commons.* errors, but import org.apache.commons.lang.* does not.
Eh, when I was debugging the other link you sent me, I swicthed from CLASSPATH to -cp, but only added it to the compiler. I'll revert the change. Just a sec.
@Dennis, yeah, my bad. Essentially that way programs would be interactive (say you wrote a brainf*** choose your own adventure game (a silly example i know)) you would want to be able to respond to additional prompts as the game runs.
@Dennis Suever's MATL online compiler uses something called "webhook" for that (more information here). I don't really know how it works, but you can ask him if interested. I had to change some simple configuration on my GitHub repository.
By default is only grabs releases, not commits. That may be a good solution to just because a language author pushed an update doesn't mean they'd necessarily want the update pulled on TIO.
The problem is that the vast majority of language authors on PPCG (myself included) don't really bother with releases. Jelly has 236 commits and not a single release.
I'm not really comfortable with forcing people to do things to their repos for automatic updates. I guess specific commit messages would be less intrusive than version numbering.
Webhooks? Travis? CI build? I'ma need a dictionary.
> Setup a webhook on github.com that will notify your server via HTTP anytime the remote repository changes and you can pull the changes upon being notified.
The best option, albeit difficult, would be to sign in via GH, and then manage your own languages from there. Autopulls are something I don't recommend.
@quartata I guess I could receive those requests on the backend server and forward them to the arena. I'm planning to use more than one arena server anyway, so I could keep one copy on the backend server and update the arenas with rsync.