maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukas Theussl (JIRA)" <>
Subject [jira] Closed: (MSITE-440) Site document validation fails if unable to retrieve schema (in offline mode)
Date Tue, 01 Jun 2010 06:36:13 GMT


Lukas Theussl closed MSITE-440.

    Resolution: Fixed
      Assignee: Lukas Theussl

I consider this fixed with MSITE-474 since no more exception occurs. Current drawback is that
validation is not possible in off-line mode, but that's another issue.

> Site document validation fails if unable to retrieve schema (in offline mode)
> -----------------------------------------------------------------------------
>                 Key: MSITE-440
>                 URL:
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>          Components: doxia integration
>    Affects Versions: 2.1
>         Environment: Maven 2.2.1
> Site Plugin 2.1-SNAPSHOT
> Doxia 1.1.2
>            Reporter: Dave Meibusch
>            Assignee: Lukas Theussl
>            Priority: Critical
>             Fix For: 2.1.1
> The changes included DOXIA-263 to validate XML documents retrieves the DTD/Schema to
validate the document.
> For example, for FML, xsi:schemaLocation=""
the Doxia FML parser will retrieve before validating
the document.
> If in offline mode, or in an environment without connectivity to, site generation
will appear to hang until the HTTP client code times out (which is many minutes for each retry)
then fail.
> Workaround: remove the schema definition from the document (and lose validation when
online and IDE editing support).
> Perhaps each Doxia parser should have some embedded schemas (for FML, at least
so the entities can be resolved locally.
> Or at least a property for disabling document validation.
> I don't think v2.1 can be released with this issue unresolved.

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