> Steinar Bang :
> Steven Huypens :
>> Hi Steinar,
>> I am not using any scopes indeed, nor any explicit logging configuration. I
>> just realized though, we sometimes see the stacktrace below in our
>> integration tests, maybe it is related to your problem. It doesn't happen a
>> lot, so I
> Steven Huypens :
> Hi Steinar,
> I am not using any scopes indeed, nor any explicit logging configuration. I
> just realized though, we sometimes see the stacktrace below in our
> integration tests, maybe it is related to your problem. It doesn't happen a
> lot, so I did not have a closer lo
> Steinar Bang :
> PS Do you do any explicit logging configuration inside the bundle, in
> addition the above code? Specifically: Do you create a LogService
> Java object that is not JavaLogServic, inside the bundle?
For my own part, I see that in December 2020 I introduced a
src/test/resour
Hi Steinar,
I am not using any scopes indeed, nor any explicit logging configuration. I
just realized though, we sometimes see the stacktrace below in our
integration tests, maybe it is related to your problem. It doesn't happen a
lot, so I did not have a closer look yet.
EventDispatcher: Error d
> Steven Huypens :
> Hi Steinar,
> Some pseudo-code :
Thanks!
It immediately answers one of my questions, which was what
resourceaccessor you use, and you use the OsgiResourceAccessor.
Back in 2017 I landed on the ClassLoaderResourceAccessor, based on the
class using the and it has worked a
Hi Steinar,
Some pseudo-code :
JdbcConnection connection = new JdbcConnection(myConnection);
Database database =
DatabaseFactory.getInstance().findCorrectDatabaseImplementation(connection);
ChangeLogParameters changeLogParameters = new ChangeLogParameters(database);
String liquibaseFilePath = "O
