JRuby 1.1.5 introduces unusual plugin dependencies in Rails

Hopefully I will explain this correctly.

We have an application that we are running as an engine in Rails, which
means that all of the application code is really contained in a plugin.
Under JRuby 1.1.5, when we start up this app. with Mongrel, we see that
our custom plugin’s install.rb file is somehow included in the
dependency tree that ActiveSupport is loading (ActiveSupport requires
each node and this is how the framework and the app. are loaded). This
was a problem because the requiring of this install.rb file executes it,
and our install.rb really shouldn’t be executed except when the plugin
is installed (which is normally the only time it’s executed).

I moved to 1.1.6 and this behavior disappeared. Not sure if this is a
known issue or not, but did want to mention it in case someone on the
list had some more insight into what was happening here. I heard tell
that there were some Rails-engine specific changes made in JRuby 1.1.5
perhaps?

Thanks,
Wes


To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email