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

Make test-harness namespaces "just" work with toplevel jack-in #3334

Open
FiV0 opened this issue Apr 25, 2024 · 3 comments
Open

Make test-harness namespaces "just" work with toplevel jack-in #3334

FiV0 opened this issue Apr 25, 2024 · 3 comments

Comments

@FiV0
Copy link
Contributor

FiV0 commented Apr 25, 2024

When running .gradlew :clojureRepl from the root I can't evaluate namespaces in the test-harness. It seems to be some source directory setup issue.

@l4e21
Copy link
Contributor

l4e21 commented Apr 26, 2024

Noting that this also applies to http-server and other modules

@FiV0
Copy link
Contributor Author

FiV0 commented Apr 26, 2024

The other modules work fine for me. @jarohen mentioned this has something to do with test sources and non test sources.

@l4e21
Copy link
Contributor

l4e21 commented Apr 26, 2024

As far as I can tell from testing, this is caused by the IDE looking for the gradlew wrapper and not being able to find this. Adding a symbolic link to gradlew on a project level fixes the issue for me in both http-server and test-harness.

I've had a look at getting our build to do this from the root project's wrapper task but it's probably not worth it compared to just adding symbolic links (or changing the place your IDE looks for the wrapper)

EDIT: Scratch the above, misread the issue and found a different one 😅 . I actually can't replicate this issue. Evaluating namespaces etc works fine for me when running clojureRepl from root level

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants