In my build file,
project A would not be built unless project B built.
This is handled using the depends attribute of target.
Forces correction of problems with the core projects.
All jars built are put/copied into the ${dist.dir} location.
All jar names are given property values e.g. ${projectA.jar.name}
Hope that helps.
T Master
----- Original Message -----
From: "Herman, Dave" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 09, 2002 11:06 AM
Subject: Inter-project dependencies?
> Hello,
>
> How do people usually handle inter-project dependencies? We have several
> interdependent projects, where building a release of project A should
> include building project B and getting the latest release of its jar file
in
> the distribution area for project A, such as this:
>
> A/
> release/
> lib/
> A.jar
> B.jar <-+
> B/ |
> release/ | (copied during A's build procedure)
> lib/ |
> B.jar --+
>
> Some possibilities I've thought of, but none of which seem particularly
> lovely, would be requiring the other projects to be in a standard
location,
> passing in a -D parameter to specify the locations of other projects, or
> keeping a text file that in source control that lists the locations of the
> dependencies.
>
> How have others dealt with this?
>
> Thanks so much,
>
> Dave Herman
> [EMAIL PROTECTED]
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
