I guess you *could* split projects into different files and use Ruby's Kernel::load to piece them together but that's definitely not a common practice in Buildr land.
alex On Mon, Jan 11, 2010 at 9:39 PM, Antoine Toulme <[email protected]>wrote: > No, buildr does not support multiple projects defined in multiple files. > On the contrary to Maven, Buildr wants to use less files and make your > build > clear for everybody. > > Note that what you are doing means that those subprojects might not be set > up correctly, in particular they might end up having their target folder in > the wrong place. > > If you think your projects should have a different lifecycle, in particular > if versioning should be different from one project to another, you should > create a buildfile per project. If you use git, note that the whole > repository needs to be tagged when releasing, and it's best in that case to > put one project and one buildfile in the repository, no more. > > Thanks, > > Antoine > > On Mon, Jan 11, 2010 at 18:30, femto Zheng <[email protected]> wrote: > > > Hello all,Does buildr supports multiple sub-project? > > I mean, more like maven's style, has buildfile/pom under > > each subproject, not in a big one file. > > But from the documentation of buildr now, I seem to only > > see the example only can use one big file in the root dir > > of all projects, > > now I use > > > > eval(File.read("subproject1/buildfile")) > > eval(File.read("subproject2/buildfile")) > > to support this. > > >
