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

Task 'exportClasspath' not found in root project 'nf-hello' and its subprojects. #18

Open
stevekm opened this issue Mar 20, 2024 · 2 comments

Comments

@stevekm
Copy link

stevekm commented Mar 20, 2024

As per the README

  1. Run Nextflow with the plugin, using ./launch.sh as a drop-in replacement for the nextflow command, and adding the option -plugins nf-hello to load the plugin:
./launch.sh run nextflow-io/hello -plugins nf-hello

I get the error

Missing '.launch.classpath' file -- create it by running: ./gradlew exportClasspath

and if I try to run the command suggested, I get another error

./gradlew exportClasspath

FAILURE: Build failed with an exception.

* What went wrong:
Task 'exportClasspath' not found in root project 'nf-hello' and its subprojects.

Ideas?

$ gradle --version

------------------------------------------------------------
Gradle 7.6
------------------------------------------------------------


$ java --version
openjdk 11.0.22 2024-01-16 LTS
OpenJDK Runtime Environment Corretto-11.0.22.7.1 (build 11.0.22+7-LTS)
OpenJDK 64-Bit Server VM Corretto-11.0.22.7.1 (build 11.0.22+7-LTS, mixed mode)

running against Nextflow version 567f5334ff0d225cd95dc7b5239c4dbd64696a9a

@drernie
Copy link

drernie commented Dec 6, 2024

Possibly related. When I run make compile I get:

./gradlew :nextflow:exportClasspath compileGroovy

FAILURE: Build failed with an exception.

* What went wrong:
Cannot locate tasks that match ':nextflow:exportClasspath' as project 'nextflow' not found in root project 'nf-hello'.

@bentsherman
Copy link
Member

I was never able to find the root cause of this issue. I would look into but now we have someone working on a more comprehensive solution for the plugin boilerplate.

In the meantime, I just use the workaround described in #13 to build and install the plugin locally. It will overwrite the actual installed version, but it works and as a bonus it allows you to test the plugin without needing to build nextflow locally. Just pin the plugin version in your config and run with nextflow.

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

3 participants