Maarten Coene wrote:
It should be ok now in trunk. I've changed to code to use standard JAXP api for
generating the report instead of using the XSLT task of Ant.
I think it's a bug in Ant 1.7.0, I'll file a bug report tomorrow
/srv/gump/public/workspace/smartfrog/smartfrog/build.xml:961: specify
the stylesheet either as a filename in style attribute or as a nested
resource but not as both
In org.apache.tools.ant.taskdefs.XSLTProcess, this message is created if
the resource and the file for the XSL transform are set.
if (xslResource != null && xslFile != null) {
throw new BuildException(baseMessage + " but not as both",
getLocation());
}
Is the problem that you cant use the task more than once without it
complaining that the style is over-defined? If so it is because XsltTask
copied the file into a resource and didnt clean up afterwards.
I will move uses to a local variable instead.
http://issues.apache.org/bugzilla/show_bug.cgi?id=43635
Short term, there is an ant1.7 only workaround; set the stylesheet using
a file resource.
