I'm currently working on ewarp, a WAR packager for Erlang apps based on Erjang, so they can be run in any Servlet container, e.g. on Tomcat running in the cloud (Amazon Elastic Beanstalk, CloudFoundry, ...). It's in the very early stages, see https://github.com/jetztgradnet/ewarp for details.
In order to package both Erjang and a OTP runtime, Krestens recent support for embedding OTP into the Erjang jar is great. These two commits change the ant build.xml to exclude some more files and add another task to create a jar file, which contains only OTP, no Erjang.
I switched Ant target names, so "otpjar" is the jar with only OTP and "alljar" is a new target, which creates a jar containing both Erjang and OTP. I also changed the name of this jar file to contain both the Erjang version as well as the OTP version.
Changed task "otpjar" to create an OTP-only jar without Erjang, which…
… can be put into the classpath. Added another task "alljar" which creates a Erjang+OTP jar.
exclude some more files: C code, C headers, Java code, examples
Merge pull request #51 from jetztgradnet/otp-jar
New build targets for packaging OTP in jar files