-
Notifications
You must be signed in to change notification settings - Fork 90
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
Gradle plugin crashes with Jackson-related stacktrace #1339
Comments
Fixes smallrye#1339 Signed-off-by: Michael Edgar <michael@xlate.io>
Fixes smallrye#1339 Signed-off-by: Michael Edgar <michael@xlate.io>
Was not fixed by #1342 Plugin does work with a sample project. Since |
@Hes-Siemelink , if you can provide a reproducer project that has this problem, I could help look at it. As you've said, it's may not an issue with the plugin, but the additional Jackson version on the classpath. If you enable debug logging when running the plugin, you should see statements like this:
where X is the jar file being added. That might help confirm what is present during the scan. |
This is what I see
Looks good to me. I will ping you if I find something that points to the plugin... For now doesn't seem to be the first candidate of causing the error. Thanks again! |
I am trying the gradle plugin but it doesn't work out of the box
Setup
main
/ 3.1.2-SNAPSHOTgradle clean build --stacktrace
Behavior
In stead of succeeding, the build fails with the following stack trace (snippet):
This can be traced down to a different version of
jackson-core
being used (that has theJSONFactory
class) vsjackson-dataformat-yaml
(that has `YAMLFactory, calling the _createContentReference() method).Plugin classpath:
Workaround
Works when I revert to Jackson 2.12.0 in the main
pom.xml
of the SmallRye project and rebuild the plugin.The text was updated successfully, but these errors were encountered: