Eliminating sleeps from runtest...

[ru...@us.ibm.com]

On Wed, 15 Dec 1999 Costin.Manolache@eng.sun.com wrote:
> Both runtest.sh are bad, not because ksh but because of that
> sleep that can't be avoided and it's either too long or too
> short.

On Wed, 15 Dec 1999 James.Davidson@eng.sun.com wrote:
>Yep... I abhor having that sleep in there. The person that gets that out
>of there and finds me gets a drink of their choice bought for them. :)

The following appears to do the trick:

   package tests.shell;

   import org.apache.tomcat.shell.*;
   import org.apache.tools.moo.*;

   public class Test {

     public static void main(String[] mooArgs) {
       String tomcatArgs[] = new String[] {};
       Startup.main(tomcatArgs);
       Main.main(mooArgs);
       Shutdown.main(tomcatArgs);
     }
   }

Any objections to my incorporating this into the build and changing
runtest.[sh,bin] accordingly?

Suggestions for the package name and/or mechanisms to distinguish arguments
 destined for tomcat from those destined for moo?

Re: Eliminating sleeps from runtest...

[Co...@eng.sun.com]

rubys@us.ibm.com wrote:

> On Wed, 15 Dec 1999 Costin.Manolache@eng.sun.com wrote:
> > Both runtest.sh are bad, not because ksh but because of that
> > sleep that can't be avoided and it's either too long or too
> > short.
>
> On Wed, 15 Dec 1999 James.Davidson@eng.sun.com wrote:
> >Yep... I abhor having that sleep in there. The person that gets that out
> >of there and finds me gets a drink of their choice bought for them. :)
>
> The following appears to do the trick:
>
>    package tests.shell;
>
>    import org.apache.tomcat.shell.*;
>    import org.apache.tools.moo.*;
>
>    public class Test {
>
>      public static void main(String[] mooArgs) {
>        String tomcatArgs[] = new String[] {};
>        Startup.main(tomcatArgs);
>        Main.main(mooArgs);
>        Shutdown.main(tomcatArgs);
>      }
>    }
>
> Any objections to my incorporating this into the build and changing
> runtest.[sh,bin] accordingly?
>
> Suggestions for the package name and/or mechanisms to distinguish arguments
>  destined for tomcat from those destined for moo?

IMHO, if you can build this into an ant taskdef we will get maximum
flexibility.

( like
 <tomcat-start dir="xxx" port="xxx" />
 <moo file="xxx" />
 <tomcat-stop />
)

Costin