On Dec 30, 2006, at 8:22 PM, Jay Bryant wrote:
I get Ant to work with Saxon with tasks similar to this one:
Disregarding my issue for a moment, I don't understand how this could
possibly work. Okay, so the Saxon JAR is on the classpath. We could even
assume it's the very first entry on
On Dec 30, 2006, at 8:22 PM, Jay Bryant wrote:
I get Ant to work with Saxon with tasks similar to this one:
Disregarding my issue for a moment, I don't understand how this could
possibly work. Okay, so the Saxon JAR is on the classpath. We could
even assume it's the very first entry o
On Dec 30, 2006, at 4:30 PM, Trevor Harmon wrote:
What about Xslt? Is it still broken?
After more investigation, I believe that Xslt is indeed broken, and
it's probably the exact same issue that afflicted Junit, as described
in bug #38799 [1]. However, I should also point out I was finally
On Dec 30, 2006, at 4:30 PM, Trevor Harmon wrote:
What about Xslt? Is it still broken?
After more investigation, I believe that Xslt is indeed broken, and
it's probably the exact same issue that afflicted Junit, as described
in bug #38799 [1]. However, I should also point out I was finally
If all you want to do is get a simple status result, you may want to look at
the task (from the ant-contrib project) and use it to set a
result property that can be queried from the calling script.
Otherwise to stay with core ANT tasks you can have the subroutine script write
their result (vi
I'm trying to use Saxon instead of the built-in Xalan processor for
the Xslt task. Supposedly, all I have to do is specify a classpath
when calling the task [1], but I've never been able to get this to
work. Ant always finds the built-in processor in its lib directory.
I see that the Ant FA
I am trying to make a java file name Proper case without inputting the file
names
ex: test.java to Test.java
The below code takes all the .java files and converts the entire filename to
upper case.
self.addMappedName(source.toUpperCase());
self.addMappedNa
