> From: Peter Donald [mailto:[EMAIL PROTECTED] > > At 09:34 AM 6/11/01 +0200, Stefan Bodewig wrote: > >Peter Donald <[EMAIL PROTECTED]> wrote: > > > >> Each project file consists of basically the following bits. > >> 1. projectrefs (if implemented) > >> 2. imports of libraries (ie like taskdef but importing all types in > >> library) > >> 3. implicit tasks (like properties and anything else we allow at > >> top-level) > >> 4. targets (that contain tasks) > >> > >> I think that it would useful to force the above order in build > >> file. So if feature is present it must be in above order. > > > >Not sure about the order of projectref vs. import, but agree with the > >rest. > > as long as they are before (3) then I am happy ;) >
But how can you pass <param> to your <projectref> if you cannot have <property> declared before hand. Same applies for the location attributes of <projectref> and so on. You should always be able to define <properties> before anything else. Jose Alberto
