I think the easiest possibility is using a :
if (file.isDirectory()) {
markerName = project.getProperty("markerfile");
markerFile = new java.io.File(file, markerName);
self.setSelected( markerFile.exists() );
}
I've created an AntUnit test ...
Jan
---8-<--
I'm trying to generate docs from modular xml files connected using
xinclue. I've been trying the Ant XSLT task, but cannot figure out how
to tell it to use Xerces xinclude support. Is there an easy way to make
the XSLT task use Xerces xinclude support?
-
On Nov 29, 2007 10:05 AM, Geoffrey Mitchell
<[EMAIL PROTECTED]> wrote:
> Sadly, the only solution I could find was to use the java task to invoke
> ant in a new JVM for each sub-project (with ant-contrib for task to loop
> through directories). I use one shared build file for all projects. I
> kn
Sadly, the only solution I could find was to use the java task to invoke
ant in a new JVM for each sub-project (with ant-contrib for task to loop
through directories). I use one shared build file for all projects. I
know this is not the "ant way", but it makes a lot more sense to me than
copy
Hello Dominique,
Thank you for your answer.
Actually I found out why my stuff was not working... I guess working long
hours on the same thing gets me blind and I did not see a simple thing:
I did not have the outtype=${debug.dir}\${exename} in the CC command.
So it never launched the linker...
On Nov 29, 2007 12:40 PM, Francisco Tolmasky <[EMAIL PROTECTED]> wrote:
> Is there any way to say:
> "Use the build file in the directory if the directory contains a properties
> file?"
I would have thought it to be possible with selectors and a mapper,
but I don't see how do it in practice. I th
I was actually able to get this running by removing the genericantfile
portion.
But I still have one remaining problem, I'd like it to only run in
directories that
have a project.properties file in them, however if I use
it tries to use
the project.properties
file as the build file. Is the
I've now changed it to:
And I am still getting the same error "ubant task calling its own
parent target." I placed an echo inside of
"Build-Project" to investigate what was going on:
It s
On Nov 26, 2007 6:30 PM, fabien_pichard <[EMAIL PROTECTED]> wrote:
> I went to http://ant-contrib.sourceforge.net/cc.html to try to understand
> how linking worked but I still cannot make it work at all...
>
> xmlns:cpptasks="antlib:org.sf.net.antcontrib.cpptasks"
> xmlns:antcontrib="antlib:net.sf
The problem is that you use the "genericantfile" attribute.
This implies the current (master) script into the projects. Therefore you'll
get a cycle between and .
Jan
> -Ursprüngliche Nachricht-
> Von: Francisco Tolmasky [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 29. November 2
My project currently uses a common build file to build a number of sub-
projects
(each of which may also have a sub-project as well). My first
inclination was thus
to use the subant task to build all these subprojects, as so (almost
straight out of
and subtask documentation):
11 matches
Mail list logo
