RE: Enhanced command line utility - great idea, more info

[Lo...@lotus.com]

Having the command line utility intelligently and gracefully accept either
a local machine's path\filename or a URL would be a great feature, and
definitely save on some support time!

Since we don't have the FAQ posted, I'll make a couple of notes for you
here:

-- We only accept URL's mainly because we simply pass them through to
Xerces, which only accepts URLs (actually a small set of local
path\filename references *do* work, but I haven't tested to see which ones
do/don't, and most don't).  So don't count on this being super-easy.

-- See org.apache.xml.utils.SystemIDResolver and
ftp://ftp.isi.edu/in-notes/rfc1738.txt for tips on URL handling.  Note that
I've heard several people say that the java.net.URL class is not a very
good example of URL handling...

-- Q: How do I submit a patch to Xalan?
A: Make your subject line start with [PATCH] and then note the filename(s)
and briefly what the patch does.
In the body of the email, describe what you patched and why, and any
questions or hints you might have for committers who will be reviewing the
patch.  Always include the patch as an attachment (or zipped attachment) to
the email: this
prevents problems with mailers that wrap long lines.  If the patch is
small, then *also* include a copy of the patch in the body of the email
itself (which makes it quicker to review).
The best way to create a patch currently (someone suggest better ways as
needed) is to use the CVS diff command like so:
  cvs diff -u FileName.java >> FileName.java.patch
This creates a _u_nified diff of your local FileName.java against the most
recent revision in the repository, putting the output into
FileName.java.patch
For hints on using CVS, see http://xml.apache.org/cvs.html

- Shane

---- you <hl...@METALMAKER.COM> wrote ----
> Oh, I get it.  Thanks for the background info!  Maybe I can get it to use
> either path/name or URI ...  :)
>
> -- Hank