ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Vogel <>
Subject RE: path/fileset and missing directories
Date Sat, 07 Jul 2001 20:49:01 GMT
Hi Larry,

I too have suffered this sort of problem, only it is a little more
pervasive because the "clean" target can scrub things referenced
elsewhere (I have a two-level build process, the top level can drive the
builds for all the subsystems, each subsystem has a build.xml that builds
that entire subsystem, a side-effect of the political climate at my current
contract).  Anyway, what I did is have my top-level check for the 
existence of the files and set a variable to "." instead of the proper
path before <ant> ing the subsystem levels.    I'm not thrilled with the
hack this implies, so I may submit a patch to allow a "nofail" attribute
on a fileset that will prevent what you are seeing...


> -----Original Message-----
> From: Larry V. Streepy, Jr. []
> Sent: Friday, July 06, 2001 9:12 AM
> To: ant user mail list
> Subject: path/fileset and missing directories
> Ok, time for my stupid question of the week.  Since the email archives
> are out of commission right now I don't feel too guilty... :-)
> I'm trying to setup a path, which is referenced numerous times in the
> remainder of the build file.  However, I want to use a nested 
> fileset so
> I can avoid listing the .zip files discretely (since they change
> depending on the platform being built on).  Here's the snippet:
> <!-- weblogic pieces of the path -->
> <path id="wl.path">
>   <pathelement location="${wl.home}/lib/weblogicaux.jar" />
>   <pathelement location="${wl.home}/classes" />
>   <pathelement 
> location="${wl.cyberplus.dir}/mssqlserver4v70/classes" />
>   <fileset dir="${wl.cyberplus.dir}/OracleJDBC/lib">
>       <include name="**/*.zip"/>
>   </fileset>
> </path>
> <property name="wl.path" refid="wl.path"/>
> Ok, works just peachy, except on a cleanly installed box wherein the
> mssqlserver and OracleJDBC directories do not yet exist. In that case,
> the build fails when trying to create the fileset because the 
> specified
> "dir" does not exist.  Part of my build process will create these
> directories (by extracting them from tar balls in the source 
> tree), but
> I can't get the build to even start in this initial state.
> So, any ideas on how to get around this problem?
> TIA.
> -- 
> Larry V. Streepy, Jr.
> Chief Technical Officer and VP of Engineering
> Health Language, Inc.  -- "We speak the language of healthcare"
> 970/626-5028 (office) 
> 970/626-4425 (fax)    

View raw message