-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Devmode should be recognizing compile-only and runtime-only dependencies #9422
Comments
Maven has the same thing (provided = compileOnly, runtime=runtimeOnly). I actually just ran into an issue caused by this with my reagument PR, we are resolving provided deps which includes graal svm, which includes a bundled old version of ASM. If I get time today I might make an attempt at this based on your PR for the 'test dep leakage' issue. |
I thought about Maven and |
I don't think we should be supplying 'provided', otherwise from the point of view of Quarkus it is the same as 'compile'. We also use provided for artifacts that we expect substrate VM to provide, which definitely should not go into the app. |
You are right, I was just thinking the same. So, yes, we should not included |
We are running into this issue, where we'd like to have some dependencies as |
As |
I use Gradle as follows: compileOnly("foo.bar")
testImplementation("foo.bar") For non-Quarkus projects, this works perfectly fine. However, when trying to run the tests in the Quarkus project, I get:
|
Could you please create a new issue and attach a reproducer? Thanks |
Turns out I was running into #39073, so a different issue than this. |
Gradle supports
compileOnly
andruntimeOnly
classpath dependencies. However, at this point our devmode support does not allow isolatingcompileOnly
dependencies from the runtime classpath.And isolate the
runtimeOnly
classpath from the compile classpath.fyi @stuartwdouglas
The text was updated successfully, but these errors were encountered: