If we were going to spend time on the build scripts, I'd vote for looking at ways to simplify them altogether rather than patching them more with timers etc.  I think once we simplify them, we'll be in a better position to sort out issues around making it run quicker.

The product/build.xml has 33 targets in it >:o .  As I see it, the whole thing is overly hierarchical with build.xml files at nearly every level + separate build.xml files for testing etc.  Many of the property names are so long that it becomes very difficult to distinguish between them. 

I think we're overly fixated with trying to make the build scripts super intelligent ala "I want to be able to run any target and have the build figure out what else needs to be run" resulting in every target being dependent on every other target up and down the build.

Sorry for going on a bit.  It's just that our build is something that drives me bats.

KISS :-*

T.

Mark Little wrote:

I'd +1 on fixing this up if it can dramatically reduce build times. Any idea what we might get it down to? I seem to recall it used to take about 7 minutes on my "old" box :-(

Mark.

On 28 Jun 2007, at 11:55, Kevin Conner wrote:

Kevin Conner wrote:

As I said, I will go through it tonight and make sure it is correct :)

I went through the build files and tidied them up but this is not the

reason for the long build time.  It appears that a number of targets are

being called more than once, caused by the build files traversing their

targets horizontally and vertically.

There are a number of tasks which can handle this, javac springs to

mind, but the majority of them do not.  The normal way of handling these

types of issue is to create a timestamp file when the particular target

executes.  This timestamp file can then be used, in conjunction with the

target requirements, to determine whether the target needs to be executed.

This could be used to shorten the build cycle, especially for repeat

invocations (i.e. rerunning tests).

Does anyone feel that this is something worth implementing at this stage?

Kev

P.S. I am sharing wireless atm so may not get any replies until tomorrow :)

-- 

JBoss, a Division of Red Hat

Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod

Street, Windsor, Berkshire,

SI4 1TE, United Kingdom.

Registered in UK and Wales under Company Registration No. 3798903

Directors: Michael Cunningham (USA), Charlie Peters (USA) and David

Owens (Ireland)

_______________________________________________

esb-dev mailing list

esb-dev@lists.jboss.org <mailto:esb-dev@lists.jboss.org>

https://lists.jboss.org/mailman/listinfo/esb-dev

----

Mark Little

mlittle@redhat.com <mailto:mlittle@redhat.com>

JBoss, a Division of Red Hat

Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in UK and Wales under Company Registration No. 3798903 Directors: Michael Cunningham (USA), Charlie Peters (USA) and David Owens (Ireland)

-- 

Red Hat:

Registered Address: Red Hat Ltd, Brian O' Donnell and Partners, 62 Merrion Square, Dublin 2, Ireland.

Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, at No. 304873

Directors: Charlie Peters (USA), Michael Cunningham (USA). David Owens, Brendan Lane