You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "Sarah McNamara (JIRA)" <xa...@xml.apache.org> on 2005/07/17 19:29:10 UTC

[jira] Commented: (XALANJ-719) Xalan-J build.xml bugs/enhancements

    [ http://issues.apache.org/jira/browse/XALANJ-719?page=comments#action_12315998 ] 

Sarah McNamara commented on XALANJ-719:
---------------------------------------

The first set of issues, namely fixing the clean target and using the filter mechanism to update the Version, manifest and entities.ent file either have, or will be done via XALANJ-2170.

> Xalan-J build.xml bugs/enhancements
> -----------------------------------
>
>          Key: XALANJ-719
>          URL: http://issues.apache.org/jira/browse/XALANJ-719
>      Project: XalanJ2
>         Type: Improvement
>   Components: Xalan
>     Versions: CurrentCVS
>  Environment: Operating System: All
> Platform: All
>     Reporter: Shane Curcuru

>
> 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).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org