Failed to read schema document `https://www.eolang.org/xsd/XMIR-0.48.2.xsd`

[volodya-lombrozo]

Recently one of the pipelines in jeo-maven-plugin failed with the following error:

-1:-1: schema_reference.4: Failed to read schema document 'https://www.eolang.org/xsd/XMIR-0.46.0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.

build.log

Moreover, it failed only on ubuntu system. On macos everything is fine.

[volodya-lombrozo]

@yegor256 Could you take a look, please? This issue blocks any progress in jeo-maven-plugin.

[volodya-lombrozo]

Where it happened:

    at com.jcabi.xml.StrictXML.<init> (StrictXML.java:122)
    at com.jcabi.xml.StrictXML.<init> (StrictXML.java:93)
    at com.jcabi.xml.StrictXML.<init> (StrictXML.java:84)
    at com.jcabi.xml.StrictXML.<init> (StrictXML.java:74)
    at org.eolang.jeo.representation.VerifiedEo.asXml (VerifiedEo.java:71)

[yegor256]

@volodya-lombrozo the URL is valid. The problem most probably is related to some instability of network connection. The best we can do is to introduce a retrying mechanism to StrictXML, but I'm not sure how exactly...

[volodya-lombrozo]

@yegor256 I believe we shouldn't rely on an internet connection here. It creates an enormous number of bugs and flaky tests. It's better to keep everything local. In other words, now we can't develop without the internet. Btw, it is often the case.

As you can see, I faced with this problem immediately.

[volodya-lombrozo]

@yegor256 btw, it might be interesting https://stackoverflow.com/questions/28267536/how-to-refer-to-a-classpath-xsd-in-xsischemalocation

[yegor256]

@volodya-lombrozo actually, not a bad idea. We can introduce new class StrictXMIR, which will use one of pre-downloaded XSD documents and avoid outbound connections.

[volodya-lombrozo]

Blocks objectionary/jeo-maven-plugin#942