[PATCH] new BuildWindow task

[Sc...@email.com]

I needed to build a new task for work.  We needed to make sure that the
builds are only run during specific times, so we don't impact our 
users.  In practice, we will be able to override this by adding an unless
property to the target.  

Attached is a fairly robust task that does this.  I included the
documentation right away as well.

Any comments?

Thanks
Scott


PS. I gave a presentation on Ant to my coworkers yesterday.  I think I
garnered some more interest.  Cool. :)

Re: [PATCH] new BuildWindow task

[Sc...@email.com]

I think I agree with what you've said.  This discussion has been had
before.  With many discussions on what is core to ant.  However, those
discussions usually end with the talk of Ant 2.0, and the move to
everything is optional, only the Ant framework is actual included. When
that happens a CJAN and/or Optional Ant Task Network (OATN) should exist
to handle these optional tasks.  This task would absolutely go there, as
well as dozens of others.  I've been following the list for a while now,
and knew what I was doing was evil :)

I think you're not being grumpy, only hoping the future arrives early, as
we all are.

Maybe now is the time to actually get the OATN and CJAN off the ground.  

Scott

On Sat, 27 Jan 2001, Ken Wood wrote:

> I'm sure the task is useful to you, and will be
> to others.
> 
> I know I'll seem like a grumpy old man, but
> I think this kind of task has no place in Ant,
> at least the main release. Here's why...
> 
> This list always seems to have debates
> about  what ant is, or is not, but the ant
> documentation begins with "Ant is a Java based build tool."
> It doesn't say ant is a build management tool, or a build
> scheduler tool, etc, etc. The docs continue, "In theory it is kind of like make
> without make's wrinkles." Well, the gnu make documentation
> says "The make utility automatically determines which pieces of a
> large program need to be recompiled, and issues commands to recompile them."
> Make also is not a build scheduler, a build manager, etc.
> 
> My point is that a build system consists of two main
> parts - the definition of what and how to build, and the
> build management, i.e., a build infrastructure. The infrastructure
> schedules builds, makes their results available, etc.
> Ant and make deal with what to build and how to do it,
> not with the build management. For example in our
> shop we had an existing infrastruture that scheduled builds,
> captured build logs, ran regression tests, captured test results,
> and make everything available via a build web site. I just
> swapped out use of 'make' with 'ant', and let the infrastructure
> do all the rest of these management tasks.
> 
> I think it's good to share this task, but I think this
> is an example of something that should be in a repository
> of tasks available for people to add to their own ant
> based system. I don't think it should be a basic part
> of ant...
> 

Re: [PATCH] new BuildWindow task

[Ken Wood <kw...@i2.com>]

I'm sure the task is useful to you, and will be
to others.

I know I'll seem like a grumpy old man, but
I think this kind of task has no place in Ant,
at least the main release. Here's why...

This list always seems to have debates
about  what ant is, or is not, but the ant
documentation begins with "Ant is a Java based build tool."
It doesn't say ant is a build management tool, or a build
scheduler tool, etc, etc. The docs continue, "In theory it is kind of like make
without make's wrinkles." Well, the gnu make documentation
says "The make utility automatically determines which pieces of a
large program need to be recompiled, and issues commands to recompile them."
Make also is not a build scheduler, a build manager, etc.

My point is that a build system consists of two main
parts - the definition of what and how to build, and the
build management, i.e., a build infrastructure. The infrastructure
schedules builds, makes their results available, etc.
Ant and make deal with what to build and how to do it,
not with the build management. For example in our
shop we had an existing infrastruture that scheduled builds,
captured build logs, ran regression tests, captured test results,
and make everything available via a build web site. I just
swapped out use of 'make' with 'ant', and let the infrastructure
do all the rest of these management tasks.

I think it's good to share this task, but I think this
is an example of something that should be in a repository
of tasks available for people to add to their own ant
based system. I don't think it should be a basic part
of ant...

ScottCarlson@email.com wrote:

> I needed to build a new task for work.  We needed to make sure that the
> builds are only run during specific times, so we don't impact our
> users.  In practice, we will be able to override this by adding an unless
> property to the target.
>
> Attached is a fairly robust task that does this.  I included the
> documentation right away as well.
>
> Any comments?
>
> Thanks
> Scott
>
> PS. I gave a presentation on Ant to my coworkers yesterday.  I think I
> garnered some more interest.  Cool. :)
>
>   ------------------------------------------------------------------------------------------------
>                                  Name: buildwindow.index.patch
>    buildwindow.index.patch       Type: Plain Text (TEXT/PLAIN)
>                              Encoding: BASE64
>                           Description: index.html patch
>
>                        Name: BuildWindow.java
>    BuildWindow.java    Type: Plain Text (TEXT/PLAIN)
>                    Encoding: BASE64
>
>   ------------------------------------------------------------------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: ant-dev-help@jakarta.apache.org