ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan.Mate...@rzf.fin-nrw.de
Subject AW: Split build file
Date Wed, 01 Sep 2004 15:27:00 GMT
If you have a project containing several modules, you can do something like
that:

root
 |  common.xml      defines the clean,compile,... as usual (with rel.paths)
 |  build.xml       the clean,...-targets:
 |                     <target name="compile">
 |                         <subant target="compile">
 |                             <fileset dir="modules/*/build.xml"/>
 |                         </subant>
 |                     <Ttarget>
 |
 +-- docs           docs about the whole project
 +-- modules        the individual modules
      +-- modA         the first module
      |     | build.xml   the whole content: 
      |     |             <project projectname="..">
      |     |                 <import file="../../common.xml"/> 
      |     |             </project>
      |     +-- src     
      |
      +-- modB      dito


Jan


> -----Urspr√ľngliche Nachricht-----
> Von: Vadim Kazakov [mailto:VadimK@quadrus.com]
> Gesendet am: Mittwoch, 1. September 2004 17:18
> An: Ant Users List
> Betreff: RE: Split build file
> 
> Wow, never noticed these since I upgraded. This is great 
> thanks. Although I still am not quite sure what subant is 
> used for. Is it used for kicking off a sub build from a bootstrap?
> 
> -----Original Message-----
> From: Jan.Materne@rzf.fin-nrw.de [mailto:Jan.Materne@rzf.fin-nrw.de] 
> Sent: September 1, 2004 9:10 AM
> To: user@ant.apache.org
> Subject: AW: Split build file
> 
> New since 1.6.
> Then you should also look at <subant>, <macrodef>, <presetdef> and
> <scriptdef>.
> 
> Jan
> 
> > -----Urspr√ľngliche Nachricht-----
> > Von: Vadim Kazakov [mailto:VadimK@quadrus.com]
> > Gesendet am: Mittwoch, 1. September 2004 17:04
> > An: Ant Users List
> > Betreff: RE: Split build file
> > 
> > That's interesting I didn't know about this task. I just 
> use the <ant>
> > task to access other files.
> > 
> > -----Original Message-----
> > From: Bill Rich [mailto:brich@webmethods.com] 
> > Sent: August 31, 2004 6:36 PM
> > To: 'Ant Users List'
> > Subject: RE: Split build file
> > 
> > You can import files to add targets to the available set. I 
> > have several
> > Ant
> > files that I have used to organize my targets because they 
> just got to
> > much
> > for one file. In my files I do the following:
> > 
> > l10nproj.xml
> >  <import file="${env.LEVTOOLSDIR}/L10NProcess/L10NProcess.xml"/>
> > 
> > L10NProcess.xml
> >  <import 
> > file="${env.LEVTOOLSDIR}/L10NProcess/L10NProcess-macros.xml"/>
> >  <import 
> file="${env.LEVTOOLSDIR}/L10NProcess/L10NProcess-tasks.xml"/>
> > 
> > L10NProcess-tasks.xml
> >  <import
> > file="${env.LEVTOOLSDIR}/L10NProcess/L10NProcess-toktasks.xml"/>
> >  <import
> > file="${env.LEVTOOLSDIR}/L10NProcess/L10NProcess-detoktasks.xml"/>
> >  <import 
> > file="${env.LEVTOOLSDIR}/L10NProcess/L10NProcess-p4tasks.xml"/>
> > 
> > 
> > I only copy l10nproj.xml into the directory where the project 
> > files are
> > stored and run it from there. When I run ant on the 
> l10nproj.xml file
> > all of
> > the targets in all the files that are imported are 
> available as though
> > they
> > were in the l10nproj.xml file. Of course you must be careful to have
> > unique
> > names for all the targets so there is no confusion as to 
> which one you
> > are
> > referring to.
> > 
> > There is no automatic "jumping" into an imported file but you 
> > should be
> > able
> > to figure out a target that will do what you want. You 
> might check out
> > <for>
> > in antContrib if you want to loop through a bunch of test cases. Or
> > perhaps,
> > just using depends on a master target will also work.
> > 
> > HTH
> > Bill 
> > 
> > -----Original Message-----
> > From: Gera, Prateek [mailto:prateek.gera@hp.com] 
> > Sent: Tuesday, August 31, 2004 4:58 PM
> > To: Ant Users List
> > Subject: Split build file
> > 
> > Hi,
> >  Is it possible to split a build project into multiple 
> files, one main
> > build
> > file and the rest smaller that do only a part of the full 
> build task. 
> > The smaller build files may not be executed independently. 
> > 
> > This will help be freeze my main build file and create 
> > smaller xml's to
> > execute any new tests as and when required.
> > Only minor changes would be required to main build file.
> > 
> > 
> > Something like this -
> > < project name="buidandtest" default="def"  basedir-"."> ...
> > ...
> >   <include file="test1.xml"/>
> > ...
> > ...
> >   <include file="test2.xml"/>
> > ..
> > </project>
> > 
> > 
> > Upon encountering <include> the execution would jump to test1.xml or
> > test2.xml I have considered using <ant> command in main file but my
> > smaller
> > build file needs to call back targets in the main file and 
> > then it will
> > get
> > too complicated.
> > 
> > 
> > Thanks
> > prateek
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For 
> additional
> > commands, e-mail: user-help@ant.apache.org
> > 
> > 
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> > For additional commands, e-mail: user-help@ant.apache.org
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> > For additional commands, e-mail: user-help@ant.apache.org
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
> 

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message