> From: Peter Donald [mailto:[EMAIL PROTECTED]
>
> At 10:13 AM 6/13/01 +0100, Jose Alberto Fernandez wrote:
> >> Why do you need ${module.dir}? References to other projects
> >> are supposed to
> >> be static, parse time values.
> >
> >I guess I do not want to say:
> >"/opt/pub/myBuildProcess/projects/predef/a.xml" over and
> over. Of course,
> >the developer next door, using a PC instead, may have to say:
> >"d:/myBuildProcess/projects/predef/a.xml".
>
> ...snip the yada yada yada...
>
> Have a look at original proposal and reasoning behind it and look at
> existing systems (includes in c, imports in java). Your
> description of this
> system is innaccurate and naive and largely your concerns are
> not valid
> given the proposal.
>
Can you show an example of why what I say is inacurate or naive?
Or why my concerns are invalid?
In the case of C and Java, both provide flags which are almost required to
resolved includes and imports respectively.
Do you suggest the same?
ant -I /opt/pub/myBuildProcess/projects/predef ....
that is the kind of stuff that should be in the build file itself.
yada, yada, yada....
Jose Alberto
> 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 |
> *-----------------------------------------------------*
>
