-
Notifications
You must be signed in to change notification settings - Fork 128
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
Avoid compiling scope test for package/run/ commands #638
Conversation
7cf7bb4
to
4b4237e
Compare
4b4237e
to
99e701f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We may want to ensure that --class-path
makes compile
print the full test scope class path, rather than the main one, when --test
is passed.
For later: maybe the new CLI option could be moved to CompileCrossOptions
. That would make most commands accept it, but we'd have to think about how each of them should use it (repl
could put test classes in the class path, publish
would publish test JARs alongside the main ones, test
could even only look for tests in the main scope if --test=false
is passed, etc.)
modules/cli/src/main/scala/scala/cli/commands/SharedOptions.scala
Outdated
Show resolved
Hide resolved
76a3846
to
00cdc4c
Compare
00cdc4c
to
7d27fc5
Compare
modules/integration/src/test/scala/scala/cli/integration/CompileTestDefinitions.scala
Outdated
Show resolved
Hide resolved
modules/integration/src/test/scala/scala/cli/integration/CompileTestDefinitions.scala
Outdated
Show resolved
Hide resolved
modules/integration/src/test/scala/scala/cli/integration/CompileTestDefinitions.scala
Outdated
Show resolved
Hide resolved
958c198
to
1697347
Compare
1697347
to
2c3daca
Compare
* Avoid compiling scope test for package/run/ * Print fullClassPath from test if someone pass --class-path * Remove shouldCompileTest from BuildOptions
No description provided.