> Steinar Bang :
> Heh... looking at the karaf.log of the integration test, it seems to actually
> work:
>
> https://gist.github.com/steinarb/445699fc4277c36a0f9b94a799da69b1#file-karaf-log-L415
> But the "No common superclass" still happens, prior to the place where
> it starts working
>
> Steinar Bang :
>>> (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!
Heh... looking at the karaf.log of the integration test, it seems to
> Steinar Bang :
> Steven Huypens :
>> (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!
Didn't help, unfortunately. So I'll keep debugging
> Steven Huypens :
> 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
Hi Steinar,
May I suggest you re-open/recreate the issue on the Liquibase bugtracker ?
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
(I
> Steven Huypens :
> Hi Steinar,
> The xsd stacktrace can be explained by this liquibase-issue I think :
> https://github.com/liquibase/liquibase/issues/2817
> They closed it incorrectly imho
The "fix" was just changed wording in the exception message...? (unless
I'm missing something...?
Hi Steinar,
The xsd stacktrace can be explained by this liquibase-issue I think :
https://github.com/liquibase/liquibase/issues/2817
They closed it incorrectly imho
Kind regards,
Steven
On Sun, Aug 14, 2022 at 8:31 AM Steinar Bang wrote:
> > Steven Huypens :
>
> > 1) The exception "No
How can I set the javax.xml.accessExternalSchema property in an OSGi
bundle, so that a Liquibase XML parser running inside that bundle will
pick it up?
Is it enough to drop a jaxb.properties file into src/resources/ of the
bundle maven project?
Thanks!
- Steinar
> Steven Huypens :
> 1) The exception "No Common Superclass:javax/crypto/SecretKey
> javax/crypto/SecretKeyFactory" is from the liquibase pro package, as
> you can see in the stacktrace. But I do not understand that, because
> that package is not part of the 4.9.1 liquibase-core.jar. It might
