ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tharp, Joshua L, SOLGV" <>
Subject RE: Clearcase and ant
Date Thu, 01 May 2003 13:27:50 GMT
I use ClearCase and ANT in my build environment. While I haven't been
interested in the CR lately, I've used it in the past. What we did to
prevent the bad build scenario was to have two different types of build.
The first, most regularly used type is the developer's build. It uses a
normal ANT target and builds the source in the current view. The
developer is responsible for knowing to use the clean target if they
roll back a version. The other build is for distributions. In this
second case, we have a script that creates a new view and performs the
build in that view. That way you only get checked-in files and are
current for the specified build config spec (in our environment that was
usually main/LATEST, but it could be any standardized config spec).

As for CRs with java builds, Rational / IBM basically admits that there
is no real good way to build java in their "Building Software" manual,
chapter 8. They claim that there are three approaches to overcome their
1. Write makefiles correctly (i.e. spell out each dependency and order
them to eliminate rebuilds and javac automatic dependency compilations).
2. Keep rebuilding until the dependencies stabilize in the CR
3. Configure clearmake to behave as make (which eliminates the behavior
of detecting a rolled-back version)

As for a hack to do what you want in an automated way... You could copy
the source to a different directory as part of the build. Then on your
next build compare the copied source from the last build with the
current source to compile and find those that are different. You may
save a significant amount of time by not looking up the config spec
rules for each file.


-----Original Message-----
From: Harry J Walsh [] 
Sent: Thursday, May 01, 2003 2:23 AM
Subject: Clearcase and ant


I'm working on a java project using clearcase for our source control.
currently use clearmake with javac to build our project.  I've recently 
started using ant and after spending quite a bit of time searching for 
information on how to integrate ant with clearcase I still haven't been 
able to successfully do it.

Clearmake doesn't use file modification dates to manage build
but ant does.

So if I checkout a file and make some changes and then built it with
it will detect the checkout as newer than the .class file and rebuild
That's fine, however if I then decide I nolonger want those changes and 
uncheckout the file it reverts to the original version and that file 
appears to have been modified before the .class file was generated so no

rebuild is performed.

I've been looking at the source for the 'depend' task and it should be 
possible to modify that to include the clearcase file version
in the depcache.  Then I would be able to detect if a file version has 
changed since the last time it was built and remove the appropriate
file or files.

However the act of finding each .java file used in the current ant
and reading the version selected by the config spec takes quite a while
run on our source tree.

So before I proceed with this mechanism I'm polling this list in the
that one of you has already solved this particular issue.  I'm aware it 
might also be possible to use clearcase triggers to remove .class files 
when a .java checkout is cancelled, but I'm sure this will be
for us as it would be difficult to determine all the scenarious in which

'older' versions of source files are failing to trigger rebuilds.

Running ant within 'clearaudit' doesn't work as each file generated
to depend on every source file accessed by the ant process.

Any ideas or suggestions would be helpful.

Harry J Walsh

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message