Version 0.7 of the gradle plugin breaks the com.moowork.node plugin

[SalomonBrys]

The plugin com.moowork.node is the plugin that is used in the Kotlin Javascript examples to run Kotlin/JS unit tests.

However, the mere fact to apply the konan plugin in a different module makes the node plugin fail.

Moere specifically, it fails to download NodeJS:

$ ./gradlew test
Starting a Gradle Daemon, 5 stopped Daemons could not be reused, use --status for details
> Task :js:nodeSetup FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':js:nodeSetup'.
> Could not resolve all files for configuration ':js:detachedConfiguration1'.
   > Could not find org.nodejs:node:6.9.1.
     Searched in the following locations:
         https://nodejs.org/dist/v6.9.1/node.module
         https://nodejs.org/dist/v6.9.1/ivy.xml
     Required by:
         project :js

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 10s

Here is a test project that demonstrates the issue.
Just run ./gradlew test

Note that this only happens if you don't have the NodeJS archive downloaded in cache, so be sure to remove it from Gradle cache before running the test:

rm -rf ~/.gradle/caches/modules-2/files-2.1/org.nodejs/

[StefMa]

I can't see your gradle files yet (because my phone can't open it 😅) but it seems it is an "issue" with gradle not with kotlin/Native. Any. Try to add gradlePluginPortal() to your repositories. That should fix that issue...

…

On Sat, May 19, 2018, 8:27 PM Salomon BRYS ***@***.***> wrote: The plugin com.moowork.node is the plugin that is used in the Kotlin Javascript examples <https://github.com/JetBrains/kotlin-examples/tree/master/gradle/js-tests> to run Kotlin/JS unit tests. However, the mere fact to apply the konan plugin in a different module makes the node plugin fail. Moere specifically, it fails to download NodeJS: $ ./gradlew test Starting a Gradle Daemon, 5 stopped Daemons could not be reused, use --status for details > Task :js:nodeSetup FAILED FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':js:nodeSetup'. > Could not resolve all files for configuration ':js:detachedConfiguration1'. > Could not find org.nodejs:node:6.9.1. Searched in the following locations: https://nodejs.org/dist/v6.9.1/node.module https://nodejs.org/dist/v6.9.1/ivy.xml Required by: project :js * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. * Get more help at https://help.gradle.org BUILD FAILED in 10s Here is a test project that demonstrates the issue <https://github.com/JetBrains/kotlin-native/files/2019723/testBug.zip>. Just run ./gradlew test Note that this only happens if you don't have the NodeJS archive downloaded in cache, so be sure to remove it from Gradle cache before running the test: rm -rf ~/.gradle/caches/modules-2/files-2.1/org.nodejs/ — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1612>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJwYe5yu_73JXcHtn9vQabpPrOfRNroGks5t0GQTgaJpZM4UFzox> .

[minamoto79]

I afraid It's problem of nodejs plugin. there is PR-296 making nodejs plugin compatible with gradle-4.5+ (gradle_metadata feature, which will be enabled by default in gradle-5.0), but it hasn't been applied yet.

[olonho]

Anyone aware of ways how to reach NodeJs plugin developers? As they ignore the pull request, it is hard do much about it.

[SalomonBrys]

I created PR-85 on JetBrains/kotlin-examples project that uses another NodeJS plugin which works with Gradle 4.6+ and therefore Kotlin/Native ,

[sandwwraith]

@SalomonBrys There is a workaround for it; add this to build.gradle of js module:

// Workaround the problem with Node downloading
repositories.whenObjectAdded {
    if (it instanceof IvyArtifactRepository) {
        metadataSources {
            artifact()
        }
    }
}

See it in action here.