Chad Woolley
Not a member
Chad Woolley's latest activity
Wednesday, January 07 2009
Sunday, January 04 2009
-
Chad Woolley commented at 11:52 AMLet me know if you need help or have problems with the patches - it is hard to tell if I have anything wrong when there are legitimately failing tests (all bran...
-
- Tag changed from continuous_integration, patch to ci, continuous_integration, patch
Here are three diffs which should apply the latest CI changes to the master, 2-2-stable, and 3-0-unstable branches
Saturday, November 22 2008
-
Chad Woolley commented at 8:53 PMThis sounds like a great idea. Just yesterday I was getting annoyed about how hard plugin dependencies are to manage compared to gems. Dependency hell....
Pleas...
Tuesday, October 21 2008
-
Chad Woolley commented at 9:42 AM@george
You can do whatever you want. You can install and/or activate ('gem' method) the gems, but point both to the same list of gems to keep it DRY (just like...
-
Chad Woolley commented at 8:06 AM@george:
If the logic for the rake gem[:*] tasks is decoupled from the initializer, it should be possible to keep the functionality with a single preinitializer...
-
Chad Woolley commented at 6:41 AMsorry, I misspoke - preinitializer.rb support was added right before 2.0. Still pre-git, though ;)
-
Chad Woolley commented at 3:25 AM@damian:
It would look like this :)
http://geminstaller.rubyforge.or...
preinitializer.rb is already in rails, has been since about 1.0, so the name should not...
Sunday, October 19 2008
-
Chad Woolley commented at 1:17 PM"It's probably easiest to think about refactoring the initializer from the huge glob of procedural code it is now, into something a little more flexible. So you...
Friday, October 17 2008
-
Chad Woolley commented at 5:53 PMand one more thought :)
This approach (making initialization not care how gems/plugins were activated, but still able to process them) would probably also make ...