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

'files' dependencies should be added to the module path when applicable #1299

Open
nlisker opened this issue Apr 7, 2024 · 0 comments
Open

Comments

@nlisker
Copy link

nlisker commented Apr 7, 2024

Dependencies declared as implementation files("lib/my.jar") are not added to the module path even if my.jar declares a module-info.

Expected Behavior

The jar should be added to the module path, just like other dependencies.

Current Behavior

The modular jar is added to the classpath.

Context

Sometimes flat files dependencies are needed, like when bundling your own dependencies. These can be modular and should be added to the module path as is done with dependencies that are taken from a repository.

Steps to Reproduce

Create a modular project (with module-info) and add a files dependency to a modular jar and a group dependency to a modular jar in a repo (jackson, junit...). Then refresh the gradle project and go to its build path and expand Project and External Dependencies; observe which dependency is on the module path and which is on the classpath.

Your Environment

Gradle 8.7
Buildship 3.1.9
Eclipse 03-2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant