ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeffrey E Care <>
Subject Re: dirset and relative path problem
Date Mon, 16 May 2005 13:10:54 GMT
Just a shot, but can you use ".." as the basedir of the dirset and then 
use include patterns that are relative to that?

Also, it really doesn't look like you're using patterns for your includes 
here...why not just use a filelist for your directories?

Jeffrey E. Care (
WebSphere Build SWAT Team Lead
WebSphere Build Tooling Lead (Project Mantis)

"Eric Wood" <> 
05/16/2005 07:40 AM
Please respond to
"Ant Users List"


dirset and relative path problem

I'm using a dirset to build a classpath:

<path id="classpath">
            <fileset dir="${dir.wc.lib}">
                <include name="**/*.jar"/>

            <dirset dir="." >
name="../WebSphereCommerceServerExtensionsData/bin" />
                <include name="../Stores/Web Content/WEB-INF/classes" />

The problem is that it doesn't seem to like the relative references of the 
embedded includes.  When I run the build.xml in debug mode I get the 

   dirset: Setup scanner in

   with patternSet{ includes: 
[../WebSphereCommerceServerExtensionsData/bin, ../Stores/Web 
Content/WEB-INF/classes] excludes: [] }

and the build fails because it can't locate classes in these directories.

It appears that it generates a patternSet from the embedded <include ...> 
elements. If I change the way I build so the pathing is fully qualified 
then I can successfully compile my code, but I really desire to reference 
these directories relatively.

Does anybody know how I can relatively  reference directories that contain 

Eric Wood

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