Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Users List" <user@ant.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
From: "Greg Irvine" <greg.irvine@thalesatm.com>
To: "'Ant Users List'" <user@ant.apache.org>
Subject: "Recursiveness" / property already used in a "generic" build...
Date: Thu, 15 Jun 2006 16:07:49 +1000
Organization: Thales ATM
Message-ID: <001201c69042$07978690$4837630a@gilap9300>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0013_01C69095.D9439690"
In-Reply-To: <OF0E3CB420.8B328503-ON88256DE2.00733909@KP.ORG>
Thread-Index: AcOuGb6Ar6Ho7IFASTa8rpQZ2HbbbYXESA2g

------=_NextPart_000_0013_01C69095.D9439690
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all.

 
I'm trying to write a generic build file that uses a properties file to
inform the generic build file of which subprojects to build. 

 
So, the build.xml loads a build.properties which has a property buildorder
which is a list of subprojects in that directory to build, and this order is
specific due to dependencies.

 
I have this working just fine (generally).

 
This works if multiple folders have the same level do the same thing.  I'm
assuming this works because once the explicit call to build Folder1 returns,
any properties set in Folder1 or lower are cleared, so when Folder2 build
loads the build.properties the buildorder property set in Folder1 has been
cleared.

 
Parent -> Build.xml explicitly calls build on Folder1 and Folder2

          Folder1 -> build.xml + build.properties (buildorder=SubFolder1,
SubFolder2, SubFolder3)

                      -> SubFolder1

                      -> SubFolder2

                      -> SubFolder3

          Folder2-> build.xml + build.properties (buildorder=SubFolder1,
SubFolder2, SubFolder3)

                      -> SubFolder1

                      -> SubFolder2

                      -> SubFolder3

 
The problem I have is that if one of those projects is in fact a folder that
itself has a list of projects to build I find the property buildorder is
already set by the parent build file and fails trying to build the same
stuff again but in the subfolder.

          Folder1 -> build.xml + build.properties (buildorder=SubFolder1,
SubFolder2, SubFolder3)

                      -> SubFolder1 -> build.xml + build.properties
(buildorder=SubSubFolder1, SubSubFolder2, SubSubFolder3)

                                      -> SubSubFolder1

                                      -> SubSubFolder2

                                      -> SubSubFolder3

                      -> SubFolder2

                      -> SubFolder3

 
i.e. Folder1 build loads buildorder from build.properties and calls
build.xml in SubFolder1 (as specific in build.properties) which tries to
load it's build.properties which tries to define buildorder and of course
can't.

Hence, the build in SubFolder1 tries to build SubFolder1, SubFolder2,
SubFolder3 as defined by the parent buildorder again instead of the "new"
SubSubFolder1.

 
Any suggestions on how to get around this would be great.

 
Thanks and regards,

 
Greg.

 
Ps. If you REALLY think Maven is a better option let me know and I'll just
have to do an ROI analysis.


------=_NextPart_000_0013_01C69095.D9439690--