ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan.Mate...@rzf.fin-nrw.de
Subject RE: Any examples of how we can simplify ant build.xml with templa tes (?)
Date Wed, 04 Feb 2004 11:46:36 GMT
See

BugZilla "Allow targets to be inherited to lower level subprojects like
properties"
  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19437

Conor started a very long thread "override" on
  http://marc.theaimsgroup.com/?l=ant-dev&m=105965265709838&w=2
  during that thread overriding targets was pointed ...


Jan


> -----Original Message-----
> From: Jan.Materne@rzf.fin-nrw.de [mailto:Jan.Materne@rzf.fin-nrw.de]
> Sent: Wednesday, February 04, 2004 12:36 PM
> To: user@ant.apache.org
> Subject: RE: Any examples of how we can simplify ant build.xml with
> templa tes (?)
> 
> 
> > On Feb 4, 2004, at 1:15 AM, Jan.Materne@rzf.fin-nrw.de wrote:
> > > child/build.xml
> > > - import the template.xml
> > > - override targets, if needed (see "Target overriding" in 
> importĀ“s 
> > > manual)
> > >     class Super { void meth(); }
> > >     class Sub
> > >       extends Super {          -->  <import>
> > >         void newMeth();        -->  <target>
> > >         void meth() {
> > >              super.meth();     -->  <antcall target="Super.meth"/>
> > >         }
> > >     }
> > 
> > Is there a way to call "super" in this scenario without using 
> > <antcall>?
> > 
> > Another interesting trick is to define "abstract" targets in 
> > the super 
> > build which require implementation in the sub build.  So 
> rather than 
> > overriding targets, I think I prefer to define pre abstract targets.
> > 
> > 	Erik
> 
> 
> So as example
> 
>    <target name="compile" description="Example of abstract target">
>        <fail>Target 'compile' not implemented</fail>
>    </target>
> 
> 
> Jan
> 

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