• r

    rp

    8 months ago
    The way I debug is how you normally debug - it just worked.
  • r

    rp

    8 months ago
    I'll check
  • ?

    user

    8 months ago
    ok thanks
  • ?

    user

    8 months ago
    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
  • r

    rp

    8 months ago
    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
  • ?

    user

    8 months ago
    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.
  • ?

    user

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

    user

    8 months ago
    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
  • ?

    user

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

    user

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