Yeah it seems like it would more efficient to just recursive copy the top level directories and then remove the files you need to exclude later and then recursive chmod them, since it looks everything is being set to 0644 anyway..
Another option which is more like mongrel / webrick is to just run the app (for war:standalone:run) out of the current prooject directory and just create the WEB-INF there, the patch for this is attached (standalone.patch). I also added in the standalone patch to use the RAILS_ENV environment variable if set rather than hard-code it to production in war_config.rb. The rails_env.patch updates the AbstractRailsServlet.getDeploymentEnvironment to use the system environment variable if in standalone mode and it's set rather than the one in the web.xml to make it more like mongrel / webrick. I'd also like to be able to easily change the default libraries, like the bcprov-jdk14 since it isn't happy on java 1.5, and I want to be able to easily set bcprov-jdk15-136.. thanks, -jeff On 5/8/07 4:21 PM, "Nick Sieger" <[EMAIL PROTECTED]> wrote: > On 5/4/07, Jeffrey Damick <[EMAIL PROTECTED]> wrote: >> Also the copy process just to run in standalone mode is extremely long if >> you have a large project.. Is anyone taking a look a this? Maybe I can help >> out in this space.. > > It's the poor speed of File.chmod (via File.install), which forks for > every file. If you want you can replace File.install everywhere in > the plugin with File.copy, if you don't need permissions to be > changed. We still need to solve this issue once and for all, possibly > giving folks an option to turn permissions changing in the war config. >
standalone.patch
Description: Binary data
rails_env.patch
Description: Binary data
_______________________________________________ Jruby-extras-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/jruby-extras-devel
