Mongock use the wrong class loader when used with Quarkus about mongock

[janknobloch]

@tms0 yes indeed im using the packageScan feature for now, I think when using addMigrationClasses you would need to search during build time for the given mongock annotations and use a buildstep in conjunction with unremovableOf to keep those files in the class path?

[tms0]

So, @tms0 , Correct me if I am wrong, but I understand you are planning to raise a PR addressing this, right?

Here you are : #664

[dieppa]

Sorry I didn't let you know, but the PR was merged and released in version 5.4.1

[dieppa]

Thanks @tms0 . I will review the PR once it's raised :)

[janknobloch]

@tms0 worked fine for me in regards to the classloader - no touches needed there - yet i had to manually force

<groupId>org.reflections</groupId>
<artifactId>reflections</artifactId>
<version>0.10.1</version>
</dependency>

as the quarkus bom forces a downgrade onto 0.9.x which broke my integration, yet im not running native - are you?
(this is actually why I haven't pushed It yet as I want to solve the issue without the need of pulling extra dependencies in to make the extension work)

[dieppa]

Thanks @janknobloch, reflections library in some of its versions, produces this error. Not sure this is the fix for native image. If @tms0 can you confirm this is(or not) a fix, would be great. Otherwise, as said, I will wait for the PR

[janknobloch]

@dieppa - sadly haven't had the time to test native for now - hope to find some time on the weekend to report back on this if my extension works at least fine in native (with the given fix) + I need to build most likely some more build steps with "keep migration files / jandex etc"

@tms0 let me know if I can be of any help,

so far my extension runs fine with the upper mentioned quick fix, if anyone has a nicer suggestion on the reflections issue e.g. maybe to overwrite the quarkus bom somehow implicitly from the extension itself and if that's the proper way on dealing with this I'm happy for any input :-)

[tms0]

Both JVM and native modes are impacted by this issue.

@janknobloch I guess you use the package scan method ? It should explain why you don't have this issue. But package scan will not work in native mode, because org.reflections use org.jboss.vfs, which is not supported by GraalVM (if I understand correctly).

[dieppa]

So, @tms0 , Correct me if I am wrong, but I understand you are planning to raise a PR addressing this, right?

[dieppa]

@tms0 Approved pipeline run 😉