forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Crossley (JIRA)" <>
Subject [jira] Commented: (FOR-889) Use by Ant of newer catalog entity resolver failing for Windows
Date Mon, 03 Jul 2006 07:10:30 GMT
    [ ] 

David Crossley commented on FOR-889:

So to summarise:

Forrest uses the entity resolver in two situations:
1) Cocoon uses it via Excalibur;
2) prior to Cocoon starting, Ant uses it for our "validate-xdocs" build target.

For the latter, we configure the xml catalogs at
(search in page for fcatalog) 
<xmlcatalog id="fcatalog" >
  <pathelement location="${forrest.core.webapp}/resources/schema/catalog.xcat"/>

On UNIX, both situations are okay with the new resolver (see unix-validate-r395116-resolver.txt).

On Windows, situation #1 is okay (see dynamic-cocoon.log) but situation #2 is broken (see

Reverting to an older version of xml-resolver trunk (r292853), situation #2 works again for
Windows (see validate-xdocs-original-resolver.txt).

Looking at ant-debug.log it seems that resolver gets confused and builds a broken "Default
BASE". We don't use xml:base in any of our xml catalogs.

> Use by Ant of newer catalog entity resolver failing for Windows
> ---------------------------------------------------------------
>          Key: FOR-889
>          URL:
>      Project: Forrest
>         Type: Bug

>   Components: XML grammars & validation
>     Versions: 0.8-dev
>     Reporter: David Crossley
>      Fix For: 0.8-dev
>  Attachments: afterUpgrade.txt, ant-debug.log, beforeUpgrade.txt, debug-new.log, dynamic-cocoon.log,
n-cyg-resolver.log, o-cyg-resolver.log, static-cocoon.log, unix-validate-r395116-resolver.txt,
validate-xdocs-original-resolver.txt, validate-xodcs-r395116-resolver.txt
> Some people on Windows report that the 'forrest validate-xdocs' task is "failing" when
we upgrade the $FORREST_HOME/tools/ant/lib/xml-commons-resolver.jar
> See discussion in:
>  [heads up] Ant upgraded, please test

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message