Hi all, I know this is a long shot, but could renaming the "Journey" module please be considered by those in a position to support it?
I've written an issue on this in the journey repo also: https://github.com/rails/journey/issues/49 Essentially our project has a model named Journey, the same as Rails 3.2's new routing driver. As a consequence we can no longer upgrade from 3.1, without changing 'journey' throughout our project. Given that our project pretty much consists of journeys, or Journey models, for which there is practically no other name in the English language, I'm sure you can appreciate how much of a PITA refactoring would be for us. Looking through Rails 3.2's fresh Gemfile.lock, its clear there are very few common nouns used to name libraries, the exception being Rack, which maybe annoyed a few data center managers but little more. As a long term strategy, I'd like to suggest avoiding generic or common nouns for projects, so as to avoid conflicts like this. Cheers, sam -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/Lq5um1WFO2UJ. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
