ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knuplesch, Jürgen <>
Subject AW: Creating Patch builds
Date Wed, 24 Oct 2007 13:52:18 GMT
We set a Label for every .java File to show which files should get into the Patch. Then we
checkout using this Label.

The advantage is, that classes that should not go into the patch are not checkouted. The problem
is, that the programmer sometimes forgets to set the Label.

Jürgen Knuplesch          
icon Systemhaus GmbH                Tel. +49 711 806098-275
Sophienstraße 40                    
D-70178 Stuttgart                   Fax. +49 711 806098-299

Geschäftsführer: Uwe Seltmann
HRB Stuttgart 17655
USt-IdNr.: DE 811944121 
-----Ursprüngliche Nachricht-----
Von: Cyriaque Dupoirieux [] 
Gesendet: Mittwoch, 24. Oktober 2007 15:15
An: Ant Users List
Betreff: Re: Creating Patch builds

Steve Loughran a écrit :
> Rishi Gogia wrote:
>> Hi
>> I am using SVN as a repository and Weblogic Integration as my 
>> application server. I have more than 10 programmers working on the 
>> same project. I wanted to know if I want to do a patch build, how 
>> would I be able to do it?
>> By Patch build I mean compiling only those files which are changed. I 
>> was able to get the files from the revision. But since the complete 
>> build takes more than 20 minutes, I need to build only the changed 
>> files and put them in their corresponding location in the ear.
>> The files which are changed can be java files as well as WSDL, 
>> Processes etc. these need to be compiled and the class file needs to 
>> be put in the ear.
>> Please suggest me a way how to do this.
>> Thanks in advance
>> Regards
>> Rishi
> This is normally called an incremental build. By default, Ant builds 
> incrementally, if all the existing .class files are there.
> Where you may have problems is that WSDL to Java may create new files 
> with new timestamps, that exactly match the previous source -your app 
> server's wsdl2java tool probably isnt dependency aware. If this is the 
> case
> 1. generate the wsdl2java output in one directory (say, build/wsdl/src 
> )
> 2. use a <copy> with the <different> selector.
> <copy todir="build/wsdl/src2" preservelastmodified="true">  <fileset 
> dir="build/wsdl/src" includes="**/*>
>   <different targetdir="build/wsdl/src2"
>         ignoreFileTimes="false"/>
>  </fileset>
> </copy>
> 3. compile the copied source
> This ensures that only generated java source files that are different 
> from the previous set are copied, and hence compiled.

    I nearly have the same problem :
    Sometimes we go and work in a customer site to make some bug fixing.
    We need to include in a jar all the classes that have changed since the last CVS update
- and we don't have the access to CVS since we are not at home...
     The CVS client we use displays in red the changed files, but I don't know how to find
them with Ant ?
    The idea to use the <copy> with the <different> selector is not to bad if
we have a copy of the sources corresponding to the CVS repository. But maybe there is a better
solution ?
    An Idea ?



Logo PCO
Burolines - 2 TER, MARCEL DORET - 31700 BLAGNAC Tél. : - Fax :
Mobile : <>
Ce message et toutes les pièces jointes (ci-après le "message") sont confidentiels et établis
à l'intention exclusive de ses destinataires.
Toute utilisation ou diffusion non autorisée est interdite.
Tout message électronique est susceptible d'altération.
La société PCO Technologies et ses filiales déclinent toute responsabilité au titre de
ce message s'il a été altéré, déformé ou falsifié.

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

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

View raw message