ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From TMo...@s-s-t.com
Subject Re: preventing ant exit
Date Wed, 18 Jul 2001 20:58:00 GMT

Gee, this is really getting way more complicated than it should be.

All I want to do is use ant for compile-debug cycles. I'm not at a rollout
phase, or a regression test phase, or a big-bad-something phase, all I'm
doing is coding at my workstation. I'm not trying to build-jar-distribute
blah blah blah blah blah.  All I'm trying to do here is just use ant for
compiles while I'm hacking away. It really is useful for that.

So I'm *not* trying to create a pause-between-targets feature, and yes, I
only want to use this with one target: compile.  Look again at my example.
Also the way I implemented this was by adding a command-line "-loop"
option, so you only have to be victimized by this feature by choice.

I may not be clear in what I'm trying to do here, let me know if I need to
explain better. And if everybody thinks it just sucks, okay, I'll keep it
to meself : )

troy







                                                                                         
                    
                    "John.Casey"                                                         
                    
                    <jdcasey1779@        To:     ant-user@jakarta.apache.org          
                       
                    yahoo.com>           cc:                                          
                       
                                         Subject:     Re: preventing ant exit            
                    
                    07/18/2001                                                           
                    
                    03:40 PM                                                             
                    
                    Please                                                               
                    
                    respond to                                                           
                    
                    ant-user                                                             
                    
                                                                                         
                    
                                                                                         
                    




this assumes that there is only one valid target to
run in the buildfile. This is not a very versatile way
to make builds IMHO. The alternative is to accept
keyboard input on which targets you want to run, and
any target in the build file would be legal. The only
problem with this is that either no target can depend
on the execution of another, or every target must have
depends statements that are complete enough to make
them valid starting points.

Conceptually, laying a buildfile bare for this type of
execution is probably not a good idea, because it
doesn't really allow for target/task reuse, and some
targets are naturally an intermediate part of the
process of building.

In order to solve all of these issues, you probably
would have to increase the complexity and decrease the
maintainability of your buildfile to the point of
being nearly unintelligible.

Just a few thoughts, of course.

Regards,
John Casey

--- TMotte@s-s-t.com wrote:
>
> shoot i'm running 1.2 ghz/512mb here.... strange
> that it does load so slow.
> maybe a disk issue.
>
> anyhow, if user presses enter then run repeat all
> targets. no pause between
> targets, wouldn't want that.
>
> out of, well, impatience, i decided to try coding
> this in. it's a fairly
> simple hack, works really well. doesn't seem to leak
> memory over time or
> anything.
>
> thanks
> troy
>
>
>
>
>
>
>
>                     "T Master"
>
>
>                     <tmaster@iknowled        To:
> <ant-user@jakarta.apache.org>
>
>                     geinc.com>               cc:
>
>
>
> Subject:     Re: preventing ant exit
>
>                     07/18/2001 02:18
>
>
>                     PM
>
>
>                     Please respond to
>
>
>                     ant-user
>
>
>
>
>
>
>
>
>
>
>
>
> That is similar to asking javac for keyboad input to
> quit after compiling.
>
> Workarounds:  kill unnecessary processes on your box
> to allow more cpu time
> to ant; upgrade your box :-)
>
> If the user did press <ente> which target would be
> run then?  The previous
> or the next in line?
>
>
>
> ----- Original Message -----
> From: <TMotte@s-s-t.com>
> To: <ant-user@jakarta.apache.org>
> Sent: Wednesday, July 18, 2001 12:58 PM
> Subject: preventing ant exit
>
>
> >
> > hi
> >
> > i'm new to ant...
> >
> > was just wondering if there was any reason nobody
> has added an option to
> > run ant in a loop. that is, the only way it seems
> to run is
> >
> >   $ant compile
> >     <barf>
> >   $ant compile
> >     <barf>
> >   $ant compile
> >   BUILD SUCCESSFUL
> >   $
> >
> > which is sort of slow on my pc because each time
> ant has to load
> > (impatience *is* one of the three pillars of
> programming.)
> >
> > better would be:
> >
> >   $ant compile
> >    <barf>
> >   q to quit, enter to continue:
> >    <barf>
> >   q to quit, enter to continue:
> >    BUILD SUCCESSFUL
> >   q to quit, enter to continue:Q
> >   $
> >
> > ?
> >
> > thanks
> > troy
> >
>
>
>
>
>


=====
John Casey

jdcasey@digitalsymbiosis.net
Omni CodeWorks, Inc.

__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/





Mime
View raw message