hmmm. Interesting. I'm not actually sure why

compileOnly

is not working. What version of Java are you using? I use:

openjdk 15.0.1 2020-10-20
OpenJDK Runtime Environment (build 15.0.1+9-18)
OpenJDK 64-Bit Server VM (build 15.0.1+9-18, mixed mode, sharing)

I was using azul. I tried switching to openjdk 15.0.1 (in Gradle Settings... in IDEA) but same error with compileOnly

I believe running in IDEA uses

./gradlew run

. When I run this at the command line, I get the same error. However,

java -classpath "./core/*:./plugin-interface/*" io.supertokens.Main ./ DEV

seems to work because it specifies

./plugin-interface/*

in the classpath

Yea. So you should use

java -classpath "./core/*:./plugin-interface/*" io.supertokens.Main ./ DEV

only.

Can I put that in IDEA somewhere so I can start with the debugger?

I have actually never tried that. So will have to see.

So how do you debug?

The way I debug is how you normally debug - it just worked.

I'll check

ok thanks

I'm confused as to how it works for you, because with

compileOnly project(":supertokens-plugin-interface")

, the plugin-interface project doesn't appear in gradle's

runtimeClasspath

Maybe I did something previously to add

java -classpath "./core/*:./plugin-interface/*" io.supertokens.Main ./ DEV

, but i just don't rememeber how. Will check and get back soon

So you want to add plugin-interface to the existing classpath right? - you can do this in Module settings Right click on the supertokens-core module in the left panel. It should give you an option to add directory.

If you need to add any other arguments apart from classpath, you can do so in your run configuration -> vm arguments

I'm new to IDEA and gradle, but my understanding is that

build.gradle

specifies dependencies, which gradle constructs its build model from. My sense, and I could be wrong, is that such dependencies should be captured only in this file, and will therefore be available both at the command-line and within IDEA (or any other IDE that supports gradle). Currently, the dependency (on plugin-interface) is in 3 places: 1)

testImplementation

in gradle, for testing only 2) in the command

java -classpath "./core/*:./plugin-interface/*" io.supertokens.Main ./ DEV

, only when

./startTestingEnv --wait

is running and with @User's suggestion, now: 3) IDEA Module settings

Module settings and Run Configurations and are just to replace the command so don't count them both...you only need one

As for build.gradle file....it references something from the classpath so it cannot work unless plugin interface is already on the classpath

What you're saying about dependencies would be fine if the gradle dependency was pointing to a repository like central and not locally from classpath.

Thanks for the help @User

Did this solve the issue @User ?

Thank you @User . Yes @User this will allow me to run/debug inside IDEA. However, this contradicts guidance from the IDEA manual: > This information is valid for projects that are built with the native IntelliJ IDEA builder. If you're using a build tool, such as Maven or Gradle, make all changes using the build file. (https://www.jetbrains.com/help/idea/working-with-module-dependencies.html)

Also: > Dependencies that you set up manually inside IntelliJ IDEA module settings will be discarded on the next Gradle project reload. (https://www.jetbrains.com/help/idea/work-with-gradle-dependency-diagram.html)

Got it! Will see what we can do about this. Thanks

I am looking into this repo and want to contribute, I have already set up the repo but don't know how to run it. https://github.com/supertokens/supertokens-auth-react

did you follow the contributing guide for it?

yes

but how to see the changes that I implemented(on browser)

Do I have to do npm start or something after the build. I am stuck there

Ahhh, got it. I was not running the node server for testing 😢

ahh.. weird.

npm run start

should have started the node server anyway