-
Notifications
You must be signed in to change notification settings - Fork 52
Improve dependency configuration #68
Comments
Plugin version 0.1.4 resolves provided dependencies just fine, while the v1.0.2 gives an error. That seems like a regression. Edit: It does not work with v0.1.4 either, it spits out a couple of lines that look like java signatures and continues, but the generated json is not correct. So basically the plugin fails in a more obvious way in v1.0.2 - But I would prefer that it worked, while we can work around the provided dependency in the gradle scripts, IDEA screws up and makes it hard to deploy the project during development :( |
You are correct, it does check only runtime dependencies. Should be a simple fix, but just need to find the time (hopefully tomorrow). |
Thank you for the quick reply! I hope it is an easy fix. I'm on vacation until next week, so do not rush it for my sake ;) |
I am having the exact same issue with 1.0.2 still doesn't resolves my dependencies properly when using
|
The fix is trivial, just creating tests to prove the issue and then can prove the fix |
Sounds great! |
Hi
I'm getting errors due to my module having a "compileOnly" dependency on something used in the controllers that the plugin should generate the swagger definition from.
It looks like the plugin always uses the "runtime" configuration, thereby missing the classes.
I'm not intimately familiar with the gradle stuff, but the dependency I need, seems to be included in the "runtimeOnly" configuration - Maybe that could be considered as well by the plugin.
I think this issue may relate to #59 where the servlet API dependencies probably also are "provided"
If this can't be handled automatically, the plugin should probably use its own configuration that extends runtime, so it is possible to control what is going on.
The text was updated successfully, but these errors were encountered: