2007/11/1, Stepan Mishura <[EMAIL PROTECTED]>: > > 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 > > >
+1 -- Spark Shen China Software Development Lab, IBM
