Skip to content
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

Could not find method layout() #6

Closed
24glinka opened this issue Sep 20, 2021 · 1 comment
Closed

Could not find method layout() #6

24glinka opened this issue Sep 20, 2021 · 1 comment

Comments

@24glinka
Copy link

Using Gradle 7.2, with this configuration:

id "com.moowork.node" version "1.3.1"
id "com.moowork.gulp" version "1.3.0"

node {
version='10.14.0'
npmVersion = '6.4.1'
distBaseUrl = 'https://nodejs.org/dist'
download = true
npmWorkDir = file('npm')
nodeModulesDir = file(npmDir)
workDir = file(npmDir)
}

I received this error:
Could not find method layout() for arguments [pattern, com.moowork.gradle.node.task.SetupTask$_addRepository_closure5$_closure7@63011f99] on object of type org.gradle.api.internal.artifacts.repositories.DefaultIvyArtifactRepository .

Java version: openjdk 15.

What could be the root cause?
Tell me what I should add as further information.

@Shuyinsama
Copy link
Member

Shuyinsama commented Sep 22, 2021

Dear @24glinka

This package has not been updated for use with Gradle 7.0+ and we have no plans to update this package any further.
We made this fork to use the original plugin with Gradle 6 + Gulp support, since then we are starting to migrate to https://github.com/node-gradle/gradle-node-plugin.

My recommendation is to start using https://github.com/node-gradle/gradle-node-plugin
They have support for Gradle 7+ and are also in active development. It should almost be a drop-in replacement.
They did remove the GulpTask in favor of the NpxTask but as far as I know if you only use node/yarn tasks you can use their plugin with very minimal changes!

This fork will be removed in the near future.

I did not foresee this package being used by other people but I will have a look at updating the README to clearly state not to use this package due to no further development in this fork.

Our apologies!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants