There was a problem how Madvoc was scanning the classpath in v3.4.4 :) As you can see from the classpath, error comes from AutomagicMadvocConfigurator
- class that scans all jars for Madvoc actions. In short, scanning process was going 'too deep'. There are two ways how to solve this:
Limit the Madvoc scanning path, to skip the eclipse jars (not recommended).
Simply use latest 3.4.5 beta snapshot (soon to be released as final). We have fixed this issue there; you can check this without our example quickstart template. As you can see in README, you can run the Madvoc example with
gradlew jettyRun
and it should work.
I hope this works for you! If not, please let us know, and we will make it work for you.