Is it no longer necessary to include the XSD into OSGi bundles?

General Discussion
1

liquibase-version: 4.31.1

Back in august of 2022 there were issues with applying liquibase changelists in OSGi and not finding the XSD to parse XML changelists with.
Load XSD files under OSGI · Issue #2817 · liquibase/liquibase · GitHub

The problem with OSGi is that classpath resources are bundle-local. I.e classpath resources can only be accessed from inside the jar file they reside in.

This means that when parsing a changelist in a classpath resource in one of my jar files it cannot find classpath resources in liquibase-core.

So what I started doing back then is to import the XSD files (or at least: one of them) into my bundle builds:
authservice/authservice/authservice.db.liquibase/pom.xml at dee5dc8c2b4cdfc57ff83a95d5ca04895f1268cb · steinarb/authservice · GitHub
authservice/authservice/authservice.db.liquibase/pom.xml at dee5dc8c2b4cdfc57ff83a95d5ca04895f1268cb · steinarb/authservice · GitHub

But today I discovered that bundles started fine without me including the XSD file.

So what I wonder, is:

  1. Is liquibase in OSGi now able to find the XSD files inside liquibase-core when parsing a changelog in a different OSGi bundle?
  2. Does liquibase go on the net to find the XSD?

If it is 1 I will stop importing XSD files.

If it is 2 I will continue to import XSD files as classpath resources in my own bundles.

Thanks!