>surprised to see that the web app process has instances of all the >builder plugins, but without their configuration loaded. It seems >like if they're going to be there they ought to be configured. > (Maybe >the plugin instances are there as a side-effect of the plugin_loader >code sitting at the bottom of project.rb?)
Historically, it's a side effect of using the same Project class in both the builder and the dashboard. We went back and forth twice on this decision during the initial development. I think, I'm getting more and more inclined to change it yet again (and have Project and DashboardProject classes, sharing a bunch of behaviors via a mixin). I don't remember any specific examples of why loading project configuration in a dashboard context was a bad idea, but it was about unacceptably restricting what a user may put in the cruise_config.rb. So, yeah, cruise_config.rb is *builder* configuration. --Alex _______________________________________________ Cruisecontrolrb-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
