If you have a repository that supports moves with retained history such as Subersion or Git, it would pay you to change the structure to reflect the standard. If you are using CVS, though, you probably don't want to do that.
There's a useful kludge you can use if you are using any Unix system or Windows/cygwin. Just write a script that creates a set of symlinks that are laid out in correct Buildr format, and distribute with the projects. So the symlink that looks like src/main/java can be somewhere else. On Sep 15, 2010, at 7:52 AM, Antoine Toulme wrote: > So where's the parent then ? The structure must be tree-like. You could > define individual projects in each of the folders, or you can create a > Buildfile in a parent project (an additional folder in the workspace) that > would refer to the children projects with a relative path set with base_dir. > > define "parent" do > > define "child", :base_dir => "../Project1" do > > end > > ... > > end > > Also, all those projects need to be in the same source control system. So > it's pretty likely that you need to fix your projects layout now rather than > later. > > Antoine > > On Wed, Sep 15, 2010 at 01:36, Rao, Kartikeya < > [email protected]> wrote: > >> Hello, >> >> I’m having trouble trying to map my project structure using buildr. >> >> >> >> Basically I have 8 projects in a flat structure like this: >> >> >> >> Workspace/Project1 >> >> Workspace/Project1 >> >> >> >> Workspace/Project1 >> >> >> >> Kartik Rao >> Lead Developer - Sales Operations >> >> News Digital Media >> >> Level 24 | 175 Liverpool Steet >> Sydney NSW 2001 >> Australia >> >> Phone | 612 8114 7291 >> Mobile | 0423 456 892 >> >> Fax | 612 8114 7405 >> >> Email | [email protected] >> >> Web | http://newsspace.com.au/digital >> >> >> >> [image: News Digital Media] >> >> >> >> ------------------------------ >> This message and its attachments may contain legally privileged or >> confidential information. It is intended solely for the named addressee. If >> you are not the addressee indicated in this message or responsible for >> delivery of the message to the addressee, you may not copy or deliver this >> message or its attachments to anyone. Rather, you should permanently delete >> this message and its attachments and kindly notify the sender by reply >> e-mail. Any content of this message and its attachments which does not >> relate to the official business of the sending company must be taken not to >> have been sent or endorsed by that company or any of its related entities. >> No warranty is made that the e-mail or attachments are free from computer >> virus or other defect. >> ------------------------------ >> >>
