>>>>> Steven Huypens <steven.huyp...@gmail.com>:
> Hi Steinar,
> May I suggest you re-open/recreate the issue on the Liquibase bugtracker ?
I'd rather create a new issue suggesting a more OSGi-approach:
1. Define all of the service interfaces in a separate osgi bundle
2. Instead of using ServiceLoader through the mediator service, create
OSGi components exposing the services that then can be injected into
user components
But I fear that this would sound too drastic to the liquibase people, so
that will be rejected out of hand.
In this scenario the parser(s) would be created inside the liquibase
bundle, and would be able to find the XSD files.
(Hm... can DS components be created in an OSGi fragment bundle? Or are
those code only? If so this could be done outside of the liquibase
project)
> Meanwhile you can build your own liquibase-core bundle using a pom.xml like
> below, you simple add your own version of
> src/main/java/liquibase/parser/core/xml/LiquibaseEntityResolver.java to the
> project
Building my own version of liquibase-core would be the last resort.
And I think that if I build my own version of liquibase-core, it would
be to be able to expose the liquibase services as OSGi services, the way
I've outlined above.
> (I noticed I've added an empty
> src\main\resources\META-INF\servicesliquibase.license.LicenseService as
> well, maybe that fixes the encryption exception)
Ah! Thanks again! I'll try that!
(I'm pretty close to get it working now... debugging exactly when the
exception happens is what I was doing now. Logging still isn't quite
right, but that is next)
