Or make "if" support "and" operation.

As we all know, ant has two build-in properties: os.name and os.arch.
BTI can compare there two properties with the ones from the "if" parameter.
In this way, it is easier to decide whether it is required to download the
archive.
The order of os.name and os.arch doesn't matter, such as

       <my-dependency-linux
           url=" http://host.of/my-dependency.zip";
           md5="87A617D7E65979AE01B5ACE4649EB40B"
           dir="my-dep-dir"
           inc="*/lib/*.jar"
           if="is.x86, is.windows"
       />

And the candidate values for "if" could be is.${os.name} or is.{os.arch}.
Any comments? Suggestions?


2007/11/1, Stepan Mishura < [EMAIL PROTECTED]>:
>
> On 11/1/07, Sean Qiu < [EMAIL PROTECTED]> wrote:
> > The following parameters from our build script could be a proper
> candidate,
> > although i think we probably will only need some of them.
> >
> >  is.windows
> >   is.unix
> >  is.linux
> >  is.freebsd
> >  is.macosx
> >  is.aix
> >  is.zos
> >  is.32bit
> >  is.64bit
> >  is.x86
> >  is.x86_64
> >  is.ia64
> >  is.ppc32
> >  is.ppc64
> >  is.s390
> >  is.s390x
> >
>
> Yep, we may also add:
> is.windows_x86
> is.windows_x86_64
> is.linux_x86
> is.linux_x86_64
>
> Thanks,
> Stepan.
>
> >
> > 2007/11/1, Regis < [EMAIL PROTECTED]>:
> > >
> > > +1
> > >
> > > Stepan Mishura wrote:
> > > > On 11/1/07, Sean Qiu <[EMAIL PROTECTED]> wrote:
> > > >> Hi, BTI gurus
> > > >>
> > > >> As we know, some tests need to start a server before process
> testing,
> > > such
> > > >> as our jetty scenario test.
> > > >> The question is sometimes the server isn't always implemented by
> java.
> > > It
> > > >> may be platform-dependent.
> > > >>
> > > >> Shall we add a new parameter to the dependence module of BTI? Such
> as
> > > >>
> > > >>    <external>
> > > >>        <my-dependency-windows
> > > >>            url="http://host.of/my-dependency.zip "
> > > >>            md5="87A617D7E65979AE01B5ACE4649EB40B"
> > > >>            dir="my-dep-dir"
> > > >>            inc="*/lib/*.jar"
> > > >>           os="windows"
> > > >>        />
> > > >>    </external>
> > > >>
> > > >>    <external>
> > > >>        <my-dependency-linux
> > > >>            url=" http://host.of/my-dependency.zip";
> > > >>            md5="87A617D7E65979AE01B5ACE4649EB40B"
> > > >>            dir="my-dep-dir"
> > > >>            inc="*/lib/*.jar"
> > > >>           os="linux"
> > > >>        />
> > > >>    </external>
> > > >>
> > > >> In this case, BTI can download only one of them according to the
> > > current
> > > >> operating system.
> > > >> Does it make sense?  Or just find a java-implemented
> > > platform-independent
> > > >> alternative?
> > > >
> > > > I think it makes sense to add it. I also thought what that and what
> > > > kind of parameter should be added. I'd propose adding *if* condition
> > > > to the current scheme. I think it is more flexible, for example
> > > >
> > > >         <my-dependency-linux
> > > >             url="http://host.of/my-dependency.zip";
> > > >             md5="87A617D7E65979AE01B5ACE4649EB40B"
> > > >             dir="my-dep-dir"
> > > >             inc="*/lib/*.jar"
> > > >             if="is.64bit"
> > > >         />
> > > >
> > > > Thanks,
> > > > Stepan.
> > > >
> > > >> --
> > > >> Sean Qiu
> > > >> China Software Development Lab, IBM
> > > >>
> > > >
> > >
> >
> >
> >
> > --
> > Sean Qiu
> > China Software Development Lab, IBM
>



-- 
Sean Qiu
China Software Development Lab, IBM

Reply via email to