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 ;) >> Also I am curious about we should resolve conflicts in names of >> types (like multiple tasks named "javac"). Should we do it in same >> way java does it? > >yes. +1 >> Also another point is should we import any types by default? > >yes. Can you explain. Which ones and how do you see that as better than placing an <import library="core" /> at top or similar? Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------*
