-
Notifications
You must be signed in to change notification settings - Fork 52
Old version of guava is causing conflicts #379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Causing conflicts where? Fabrikt should not be on any runtime class paths. |
The conflict is when fabrikt is used via the gradle plugin, alongside a plugin that depends on a newer version of guava. See this issue for details: acanda/fabrikt-gradle-plugin#96 If you don't want to accept this change it's fine, the workaround is to use the custom task, which is not too painful. However, I think it would be best if this issue was fixed, because when I ran into this issue it was not at all obvious what was wrong, and it took me a few hours to track it down. The symptom is that all gradle tasks start failing with the error |
No problem accepting PRs, was just curious. I'm following this on my phone so maybe missed some context. Will review PR later. Thanks for the contribution |
Uh oh!
There was an error while loading. Please reload this page.
While trying to use the gradle plugin, I came across an issue caused by fabrikt having a transitive dependency on an old version of guava. See acanda/fabrikt-gradle-plugin#96
fabrikt has a transitive dependency on guava 18:
One way I've solved this before is by relocating the package so that both versions can coexist in the classpath. This is probably the most straightforward solution.
Another option is to upgrade
org.eclipse.xtend.lib
to the latest version, which depends on guava 33. This option doesn't seem so good because the reprezen dependencies seem to be unmaintained, and would probably need to be forked. There is a kotlin fork of the reprezen stuff which could be tried too. This is probably a better long-term plan, but not something I can commit to at this point.I'll start putting together a PR for the package relocation, but wanted to open this issue for discussion in case you want to take a different route.
The text was updated successfully, but these errors were encountered: