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

Provide option to leave certain modules in the classpath #90

Open
tobiasdiez opened this issue May 6, 2019 · 1 comment
Open

Provide option to leave certain modules in the classpath #90

tobiasdiez opened this issue May 6, 2019 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@tobiasdiez
Copy link

As of now, every dependency (module/jar file) is placed in the module path. However, some legacy libraries are not yet compatible with the module system, and for these cases it would be easiest to leave them on the classpath (for example, if a jar file does not provide an automatic module name but it's file name is invalid for the module system). Could you please provide an option to specify a list of dependencies that should stay on the classpath.

I think the code related is the following:

"--module-path", execTask.getClasspath()
.filter(patchModuleExtension::isUnpatched
).getAsPath(),

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants