xsds hosted on osgi.org are no more available
Created by: apupier
Describe the bug I'm pretty sure that previously several xsds were hosted on osgi.org; For instance https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
there is now a 404 reported. Our test suite started to fail between the 12th February and the 2nd of March
To Reproduce Steps to reproduce the behavior:
Expected behavior
the xsd to be available
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
Smartphone (please complete the following information):
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
Additional context
the side effect that helped me to detect it was this problem that appeared:
Expecting empty but was:<[{"lspDiagnostic"=Diagnostic [
range = Range [
start = Position [
line = 22
character = 1
]
end = Position [
line = 22
character = 10
]
]
severity = Error
code = null
codeDescription = null
source = "xml"
message = "Error while downloading 'https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd' to /home/jenkins/.lemminx/cache/https/www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd."
tags = null
relatedInformation = null
data = null
], "severity"=2, "charStart"=1112, "languageServerId"="org.eclipse.wildwebdeveloper.xml", "Creation time: "=1614847859098L, "charEnd"=1121, "resource affected"="/home/jenkins/workspace/jbosstools-fuse_PullRequest-OnlyTemplates/editor/tests/org.fusesource.ide.projecttemplates.tests.integration/target/work sp@cé/FuseIntegrationProjectCreatorRunnableForSimpleIT-SimpleBlueprintProject-2.18.1.redhat-000026/src/main/resources/OSGI-INF/blueprint/blueprint.xml", "message"="Error while downloading 'https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd' to /home/jenkins/.lemminx/cache/https/www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd.", "lineNumber"=23, "resource affected content"="<?xml version="1.0" encoding="UTF-8"?>