On Wed, 17 Sep 2003 07:57 pm, Stefan Bodewig wrote:
> (1) The current build file (the one intially loaded) should be added
> to the list of already imported files implicitly so it doesn't get
> loaded twice at all.
>
> (2) circular imports look like a bug to me - the build should fail.
>
+1 to bot
On Wednesday 17 September 2003 14:18, Stefan Bodewig wrote:
> On Wed, 17 Sep 2003, Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote:
> > Wait, you said that it prints out:
> >
> > "Skipped already imported file build.xml"
> >
> > This means that the current file is *not* imported twice... how do
> > yo
On Wed, 17 Sep 2003, Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote:
> Wait, you said that it prints out:
>
> "Skipped already imported file build.xml"
>
> This means that the current file is *not* imported twice... how do
> you gather that it executes the import once?
ISTR Peter said it would be
peter reilly wrote:
On Wednesday 17 September 2003 14:00, Nicola Ken Barozzi wrote:
Stefan Bodewig wrote:
...
I'm not sure. Even if you think the current "flat" import rules are
correct, (1) should be addressed IMHO.
Wait, you said that it prints out:
"Skipped already imported file build.xml"
This
On Wednesday 17 September 2003 14:00, Nicola Ken Barozzi wrote:
> Stefan Bodewig wrote:
> > On Wed, 17 Sep 2003, Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote:
> >>Stefan Bodewig wrote:
> >>>I feel this is wrong for two reasons:
> >>>(1) The current build file (the one intially loaded) should be
> >
Stefan Bodewig wrote:
On Wed, 17 Sep 2003, Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote:
Stefan Bodewig wrote:
I feel this is wrong for two reasons:
(1) The current build file (the one intially loaded) should be
added to the list of already imported files implicitly so it
doesn't get loaded twice
On Wed, 17 Sep 2003, Nicola Ken Barozzi <[EMAIL PROTECTED]> wrote:
> Stefan Bodewig wrote:
>> I feel this is wrong for two reasons:
>> (1) The current build file (the one intially loaded) should be
>> added to the list of already imported files implicitly so it
>> doesn't get loaded twice at all.
Stefan Bodewig wrote:
Currently a build.xml with
will print a warning "Skipped already imported file build.xml" and end
as a successful build after executing the import once.
Correct.
I feel this is wrong for two reasons:
(1) The current build file (the one intially loaded) should be added
to
> Currently a build.xml with
>
>
>
>
>
> will print a warning "Skipped already imported file build.xml" and end
> as a successful build after executing the import once.
>
> I feel this is wrong for two reasons:
>
> (1) The current build file (the one intially loaded) should be added
> to t
