options.xmlc

Jeremy Ferry <[email protected]> Sun, 19 Oct 2003 19:20:32 -0500
Newsgroups gmane.comp.java.enhydra.general
Message-ID <[email protected]>
Hi fellas,

I was having a problem getting the xmlc option -urlregexpmapping to work on 
any files not in the root level resources directory. In the past, the 
options.xmlc file would get applied recursively to all files in 
subdirectories of my resources directory but that isn't happening now. I 
fixed it with a minor tweak to the build.xml file. Because of this property:
 
  <property name="xmlc.options.file"
        location="options.xmlc"/>
 
It appears that ant is only looking for options.xmlc in the directory relative 
to the particular file that it's compiling. I changed this so that it looks 
for the options.xmlc in the top level resource directory by moving:

    <property name="resources.dir"
        value="resources"/>

above the xmlc properties and changing the xmlc.options.file property to:

    <property name="xmlc.options.file"
        location="${resources.dir}/options.xmlc"/>

Maybe this is just my preference but I think that it would be safe to assume 
that an application is generally only going to have one options.xmlc file for 
the entire app instead of one per subdirectory. I could be wrong but I 
thought at one time we were able to have any number of options files and if 
there wasn't one in the present directory, xmlc would climb the directory 
structure until it found one. Am I doing something wrong that makes this no 
longer work or am I just imagining that this feature existed?

Jeremy