DO NOT REPLY [Bug 5208] New: - Xalan-J build.xml bugs/enhancements

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5208>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5208

Xalan-J build.xml bugs/enhancements

           Summary: Xalan-J build.xml bugs/enhancements
           Product: XalanJ2
           Version: CurrentCVS
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Xalan
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: curcuru@apache.org


There are a number of current oddities or small features I'd like to get added 
to the Xalan build process but may not get to myself, so I thought I'd list 
them here.

- clean target does not properly clean the following directories:
? src/javax
? src/org/w3c
? src/org/xml
? xdocs/style/graphics
? xdocs/style/resources

- build.xml should be the sole place that version numbers or product names are 
encoded:
This will require using filtering for a number of files to stick the version 
number(s) in before using them - sort of like the xml-commons/java/build.xml 
file does.  The trick is the most effective way to do it.  This should include 
at least the following files:
src/org/apache/xalan/Version
src/MANIFEST.MF, manifest.xsltc
xdocs/sources/entities.ent

- build.xml should be confirmed to work with both an externally-installed copy 
of Ant (i.e. not using our build.bat/.sh files) and with Crimson instead of 
Xerces
(This requires making sure we appropriately use explicit classpaths inside of 
build.xml, and testing with Crimson; the parser difference might include code 
changes to our xerces integration parts).