Yes, I used the most recent marketplace version as well as locally compiled it from the source code, as suggested by @Seaside. The debug version doesn’t mention anything.
When a pre-compiled JAR is stored in the right folder, JRule loads it and prints to the console (Info) information about the loaded rules, e.g., the number of rules it could load.
With that, we know that something was processed. In my case, after migrating to 4.2.0, after JRule is loaded, it doesn’t print anything about the precompiled JAR. It’s as if it couldn’t find it. From that, I had an indication that something was wrong. Setting JRule to debug mode didn’t print anything special when the pre-compiled JAR should have been loaded or when I expected the rule to be executed.
In the most basic form, we can store the .java files directly in another folder and JRule compiles them. I had never done this before (as I don’t program in Java but in Scala, so I need to pre-compile the JAR), but that didn’t produce any output in the console or execute the rule. There was no indication that a new .java file was compiled by JRule, which is what I would have expected.
The last time JRule was updated in the marketplace was before 4.2.0 was released and my pre-compiled JAR didn’t change either. The only different thing is the upgrade from 4.1.3 to 4.2.0.