Forum: Ruby Rake best practices for managing multi-directory project?

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Df31a543d684be5fd6bc6c188d378615?d=identicon&s=25 Stuart Hungerford (Guest)
on 2006-03-14 01:09
(Received via mailing list)
Hi,

I'm currently working on a project with a number of "modules"
in different directories.  I'm using Rake to manage the running
of the module services in the correct order.

I have a directory structure something like this:


      /project
         +-- Rakefile

         +-- module A
               +-- module A files
               +-- tasks.rake

         +-- module B
               +-- module B files
               + tasks.rake

         +-- module C
               etc

So each module directory has its own tasks.rake file and all
the SQL, shell, Ruby etc scripts needed to implement the
service it provides.  Each tasks.rake uses Rake namespaces
fully to avoid any task name ambiguity across the project.

The "top level" Rakefile in /project uses Rake imports to
bring each module tasks.rake file into it and make them
available from the command line.

Are there any Rake best practices or idioms or patterns that
I could be applying in this situation?

For example, in my current setup the top level Rakefile needs
to setup module paths as global variables so the tasks.rake
files look in their own directory for script files and not the
top level directory--which seems a bit clunky.

Any advice from people using Rake for similar projects would
be much appreciated.

TIA,

Stu
This topic is locked and can not be replied to.