So what does no comment from a "heads up" message mean. Here is another way to see if the catalog entity resolver is not working.
If you are on a superfast connection you might not notice the slowdown in Forrest while it gets each DTD. You will notice if on a dial-up connection. So would someone on Windows please verify. If no-one bothers to check, then i am going to need to do extra work to study the huge apache.org HTTP access logs to make sure that it is not getting hits. -David David Crossley wrote: > The last time that we tried this, everything worked fine > on UNIX but broke on Windows. Please ensure that it works > for you. Do 'build test' and use 'sudo ngrep dtd' to make > sure that there is no network traffic. > > ngrep.sf.net > > -David > > > Author: crossley > > Date: Fri Sep 30 23:16:38 2005 > > New Revision: 292929 > > > > URL: http://svn.apache.org/viewcvs?rev=292929&view=rev > > Log: > > Upgrade from xml-commons-resolver-1.1 to > > xml-commons-resolver-1.2-dev-r292853 > > prerelease. > > > > Added: > > forrest/trunk/lib/core/xml-commons-resolver-1.2-dev-r292853.jar (with > > props) > > forrest/trunk/lib/core/xml-commons-resolver-1.2.jar.license.txt (with > > props) > > Removed: > > forrest/trunk/lib/core/xml-commons-resolver-1.1.jar > > forrest/trunk/lib/core/xml-commons-resolver-1.1.jar.license.txt
