Zetten commented on issue #3565: URL: https://github.com/apache/incubator-kie-kogito-runtimes/issues/3565#issuecomment-2984898442
I've been wrestling with a migration of a Kogito+Quarkus service from Maven to Gradle (alongside/after an upgrade to 10.0.0), and I'm seeing the same behaviour described by @deepakkapoor23 in https://github.com/apache/incubator-kie-kogito-runtimes/issues/3565#issuecomment-2221492957. That is, the `build/generated/sources/kogito` directory doesn't get created, and therefore my processes' REST endpoints aren't registered, and so on. _However_ when building with `./gradlew :my-module:assemble -Dorg.gradle.debug=true --no-daemon` and attaching a debugger I noticed that stepping through [ProcessCodegen#ofCollectedResources](https://github.com/apache/incubator-kie-kogito-runtimes/blob/10.0.0/kogito-codegen-modules/kogito-codegen-processes/src/main/java/org/kie/kogito/codegen/process/ProcessCodegen.java#L112) suggested that my .bpmn2 files were being detected. And sure enough, the codegen task picked them up and I got a working service at the end. In my tests it was pretty consistent: `-Dorg.gradle.debug=true` (even with no breakpoints) = working, regular build = not working. Could there be a race condition or timing issue in the Quarkus BuildItems? Perhaps there needs to be an explicit dependency on whatever is populating `build/resources/main` (as that seems to be where the .bpmn2 files are picked up from)? I'm happy to dig further, but perhaps this helps @mcruzdev! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
