ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Gainty <>
Subject RE: Use of Sleep
Date Mon, 01 Jun 2009 18:05:30 GMT

the closest I've seen for Windows to daemon or & is START /BELOWNORMAL option:
START ["title"] [/Dpath] [/I] [/MIN] [/MAX] [/SEPARATE | /SHARED]
      [/WAIT] [/B] [command/program]

    "title"     Title to display in  window title bar.
    path        Starting directory
    B           Start application without creating a new window. The
                application has ^C handling ignored. Unless the application
                enables ^C processing, ^Break is the only way to interrupt
                the application
    I           The new environment will be the original environment passed
                to the cmd.exe and not the current environment.
    MIN         Start window minimized
    MAX         Start window maximized
    SEPARATE    Start 16-bit Windows program in separate memory space
    SHARED      Start 16-bit Windows program in shared memory space
    LOW         Start application in the IDLE priority class
    NORMAL      Start application in the NORMAL priority class
    HIGH        Start application in the HIGH priority class
    REALTIME    Start application in the REALTIME priority class
    ABOVENORMAL Start application in the ABOVENORMAL priority class
    BELOWNORMAL Start application in the BELOWNORMAL priority class
    WAIT        Start application and wait for it to terminate

could you specify the definition of BOM?
Bill of Ordered Materials
Byte Order Mark
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten
wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist
unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet
keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen
wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire
prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe
quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information
seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les
email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune
responsabilité pour le contenu fourni.

> Date: Mon, 1 Jun 2009 09:48:53 -0700
> From:
> Subject: Re: Use of Sleep
> To:
> Will "updates" get rid of files that got deleted from the repository?  I don't like not
having an accurate BOM.  I want to know every file and what version of that file makes up
my build.  When I remove the directories and re-check my files out every time, I'm afforded
the abiility to keep an accurate BOM and know that the BOM represents the product exactly.
 Otherwise, what confidence can I lend the customer that I know what I delivered to them?
> ________________________________
> From: David Weintraub <>
> To: Ant Users List <>
> Sent: Monday, June 1, 2009 9:19:16 AM
> Subject: Re: Use of Sleep
> On Mon, Jun 1, 2009 at 10:39 AM, Eric Fetzer <> wrote:
> > A good piece of the time, David, is allocated to check out of A LOT of
> > code.  It also ftp's some very large files over a WAN.  As I take over these
> > builds, I will be digging further in where all the time is going, but for
> > now, I'm just trying to get rid of totally unnecessary aspects of the build.
> I normally don't have Ant do my checkouts since you first have to checkout
> the build.xml file to do the initial checkout. We use Hudson for our
> continuous integration, and Hudson handles the checkouts for us. That way, I
> don't even have to define a checkout task in our build.xml file. (See <
>>). You might want to switch from checkouts to
> updates since updates only update changed files, and don't checkout
> everything from scratch again.
> There are specific Ant checkout tasks for various version control systems,
> but I usually don't find them any faster than <exec>. Unless the <exec> task
> runs in the background (spawn="true"), it should wait for the <exec> task to
> complete. That means you shouldn't be having <sleep> tasks to wait for the
> checkout to complete.
> You normally run an <exec> task in the background when you're doing things
> like starting up a server, so you can run your tests. Otherwise, the default
> is to wait for the <exec> command to complete. BTW, there is a "timeout"
> parameter for the <exec> task that can help kill an otherwise lollying
> program, but it has a bit of trouble on Windows sytems.
> Best of luck speeding up your build. When I first got to my current job,
> builds took 30+ minutes to complete. I rewrote the build.xml file from
> scratch, and speeded it up to only "12 minutes". Meanwhile, we've pulled
> projects out of our main build, and each one of these build in under 2 or 3
> minutes. The "big" project still takes about 9 minutes to build. Not where
> I'd like it, but much better than it was before.
> My experience shows that when builds take forever, developers simply don't
> test as well, and your code gets sloppier.
> -- 
> David Weintraub

Hotmail® has a new way to see what's up with your friends.
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message