Hi Alex and Dominic,

Thanks! I will try it out at home! 

Alex, do you also happen to know how to get rid of those *.mop/pom files? I 
just do :package :swf but I still end up with those files. I have no clue what 
I need to do with a those files for *.swf or *.exe file :/

My other question will general packaging questions but I first want to get this 
working. I think I have a really nice experiment project to learn Buildr.

----- Original Message -----
From: "Alex Boisvert" <[email protected]>
To: [email protected]
Sent: Thursday, 6 October, 2011 2:54:03 PM
Subject: Re: How to make Buildr make with subprojects

You can override the location of a project by passing the :base_dir option
during project definition,

define :foo, :base_dir => 'somewhere/else' do
  p "base dir is " + project.base_dir
end

alex

On Thu, Oct 6, 2011 at 2:42 AM, Sprog : Weyert de Boer <[email protected]>wrote:

> Hello,
>
> I am currently experimenting with Buildr in combination with Buildr-AS3.
> Only I am having some issues with  Buildr because of our corporate policy.
> In our policy is outlined how a project should be structured. Every project
> has the following structure:
>
>  E:\[project_name]
>      - workspace (Eclipse project folder)
>
> Now if you have submodules then these are considered as a normal project.
> Only the way Buildr works is that it expects subprojects to be a child
> directory of the main project. What's the best way to solve this problem? As
> temporary solution I moved the project to my personal computer and put all
> the subdirectories into the main project. But I would like to be able to do
> this at work. How can I do this? Using ../../my_subproject didn't work as
> project name
>
> My last question for today is how can I get rid of the *.pom files that
> Buildr (or Buildr-AS3) creates? I don't need those files...
>
> Thanks for your help!
>
> --
> [Beep]
>
> --
> Sprog : Weyert de Boer
> Flash Designer/ Developer : Nothing
> [email protected] : www.nothing.ch
>
> Fon +41 31 384 10 10
> Fax +41 31 384 10 40
>

Reply via email to