On Fri, Jun 27, 2008 at 12:42 PM, Steven Guitar <[EMAIL PROTECTED]> wrote:
> So, to keep up with dependancies would you have tasks in project A that
> builds each dependency, or have a list in a properties file and read from
> that, building each one?
Best way to deal with dependency is to build
Ok. That's what I figured.
So, to keep up with dependancies would you have tasks in project A
that builds each dependency, or have a list in a properties file and
read from that, building each one?
My goal is to have really generic scripts that can build ears, wars,
or jars.
Sent from
On Fri, Jun 27, 2008 at 11:11 AM, Steven Guitar <[EMAIL PROTECTED]> wrote:
> I am working on some build scripts for projects that have a dynamic listing
> of dependancies.
>
> when i try to compile project A that depends on project B, there is not a
> way for me to know which project to compile fir
I am working on some build scripts for projects that have a dynamic
listing of dependancies.
when i try to compile project A that depends on project B, there is
not a way for me to know which project to compile first (short of
having the developer keep track of it in a properties file) - so
