-
Notifications
You must be signed in to change notification settings - Fork 181
Invocation of Task.project at execution time has been deprecated. This will fail with an error in Gradle 10.0. #21489
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
About the warnings, they are fixed in 24.8 by the changes introduced to support the configuration cache (#21022). However, I can't see any errors related to Jackson build the Gradle starter project for production. |
How can I use 24.8 (24.8.0.alpha1) ? (Does Vaadin lib 24.7.x work with Gradle plugin 24.8 ? ) Since my colleague is absent, I cannot provide Jackson details at this time. |
You can use 24.8.0.alpha7 by adding the pre-releases plugin repository in the to Gradle settings file.
However, I cannot 100% assure that the 24.8 plugin will work with 24.7. About Jackson, I wonder if there's a chance your project is pining a version that is older than the Vaadin supported one. |
I can't integrate 24.8.0.alpha7. I have to wait for the stable version. The Vaadin update will have to wait. We always have a lot of trouble with Gradle, and especially with Vaadin. |
@gastendonk thanks for the ticket and your feedback! Could you please share with us what are the main pain points for you when using Gradle with Vaadin, what could we improve? |
@mcollovati When will plugin 24.8 be released? |
The first beta release is coming soon. GA is planned around the middle of June |
Uh oh!
There was an error while loading. Please reload this page.
Updating to newer Vaadin version and so newer Gradle version.
Jenkins reports this:
How do I solve this Vaadin problem?
Here some content of i1-webapp/build.gradle:
We had to add
classpath 'com.fasterxml.jackson.core:jackson-core:2.18.3'
to the settings.gradle dependencies to make the new Vaadin build work. Can you explain me why is this necessary?The text was updated successfully, but these errors were encountered: