Spring application with spring enabled plugins about pf4j-spring HOT 2 CLOSED

@decebals for info I found the solution to this problem. It turns out the project appeared to be working as the plugins were just being picked up from the classpath. However on debugging the plugin loading a bit more closely I found that the plugin classes were not being fired up correctly (which explains my confusion around the .log messages from BidvAliasLoaderPlugin not being printed out on startup.)

In order to get them started correctly I needed to set the -Dpf4j.pluginsDir on the spring boot application when starting it up. I added a jvmArgs argument to my bootRun command like this:

bootRun {
    classpath += configurations.provided
    jvmArgs = [ "-Dpf4j.pluginsDir=${rootDir}/internal-plugin/build/libs" ]
}

And this meant the SpringPlugin is now loaded correctly and works as expected.

from pf4j-spring.

@michaelruocco
I will try to help. I wrote in a comment (I didn't find the link) that I am not expert in Spring, so, from this reason I don't add to much comments on this subject (PF4J in Spring).
Maybe other people that use PF4J in Spring applications can help us to improve the interoperability between PF4J and Spring.

from pf4j-spring.