I see your point. Even if the functionality was something you would
support, I'm not sure there's anyone willing to put in the time to
figure it out. But you never know. Like I said before, it could be
an option. So, if someone actually did the work, and it passed
rigorous testing, the fu
I think that it is the jpackage packaging of ant that
is used here. (It was the case for RedHat/Fedora),
jpackage has a number of packages for ant corresponding
to the .jar files in $ANT_HOME/lib, however it does
not follow the same directory layout as ant, and
thus jpackage version of ant does no
Peter Reilly wrote:
You are using the jpackage version of ant.
I do not know why it does not pick up the regex
that is part of java since java.1.4.
You use the ant version of ant.
Download ant 1.7.0, (say to /usr/local/java/ant1.7.0),
set ANT_HOME (export ANT_HOME=/usr/local/java/ant1.7.0)
upda
You are using the jpackage version of ant.
I do not know why it does not pick up the regex
that is part of java since java.1.4.
You use the ant version of ant.
Download ant 1.7.0, (say to /usr/local/java/ant1.7.0),
set ANT_HOME (export ANT_HOME=/usr/local/java/ant1.7.0)
update PATH (export PATH=
Hi,
i have problems installing openMDX. I'm running ant 1.6.5 from the ubuntu
repository. This is the error message:
BUILD FAILED
/usr/src/openmdx-1.12.1/ant/etc/ant/build-library.xml:215: No supported
regular expression matcher found
ant -diagnostics says:
replaceregexp : Not Available
Prashant wrote:
[Wild guess] I am not sure if the following Xerces Bug on attribute
order preservation is relevant here.
http://issues.apache.org/jira/browse/XERCESJ-863
-Prashant
Its effectively part of the XML spec. You cannot even guarantee that a
SAX parser will send you events in the
[Wild guess] I am not sure if the following Xerces Bug on attribute
order preservation is relevant here.
http://issues.apache.org/jira/browse/XERCESJ-863
-Prashant
Jacob Kjome wrote:
seems to have a problem with resolution of attributes within the
current element. It appears to resolve the
Jacob Kjome wrote:
At 05:22 PM 1/22/2007, you wrote:
>
>It's not a solvable problem. How do you resolve this:
>
>
>
I would argue that's not a relevant problem. First of all, no one would
write that because it is meaningless. Secondly, it might go like this...
1. parse 'a'
2. can'
Jacob Kjome wrote:
I think Brian is correct. XML attributes have no defined order other than the
obvious alphabetical order, which might be an implementation detail. Even so,
I wonder if logic could be written to maximize resolution. If a property is
found to not be resolved, it could be defer
