[Excalibur] - Instrument-client's dependance on AltRMI

[Paul Hammant <Pa...@yahoo.com>]

Leif,

If the altrmi jars are missing, then the buildfile barfs at parse stage 
as the taskdef is invalid.  By moving the taskdef to another build file 
and delatating to it, the barf does not happen, and thus a warning is 
possible.

Thoughts?

- Paul

Index: build.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-excalibur/instrument-client/build.xml,v
retrieving revision 1.9
diff -r1.9 build.xml
64,68d63
<
<     <taskdef name="altrmiproxies"
<         
classname="org.apache.commons.altrmi.generator.ant.AltrmiProxyTask">
<         <classpath refid="project.class.path" />
<     </taskdef>
116d110
<
121,128d114
<         <mkdir dir="${build.genjava}"/>
<        
<         <delete>
<             <fileset dir="${build.genjava}" 
includes="AltrmiGenerated*.java"/>
<         </delete>
<         <delete>
<             <fileset dir="${build.classes}" 
includes="AltrmiGenerated*.class"/>
<         </delete>
130,136c116,117
<         <altrmiproxies genname="InstrumentManagerClient"
<             srcgendir="${build.genjava}"
<             classgendir="${build.classes}"
<             
interfaces="org.apache.avalon.excalibur.instrument.manager.interfaces.InstrumentManagerClient"
<             
additionalfacades="org.apache.avalon.excalibur.instrument.manager.interfaces.InstrumentableDescriptor,org.apache.avalon.excalibur.instrument.manager.interfaces.InstrumentDescriptor,org.apache.avalon.excalibur.instrument.manager.interfaces.InstrumentSampleDescriptor">
<             <classpath refid="project.class.path" />
<         </altrmiproxies>       
---
 >         <ant antfile="altrmiproxies.xml" target="altrmiproxies"/>
 >    

CVS command finished execution