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.

Sign up for GitHub

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

Jump to bottom

Add handling for pom dependencies #144

Closed
AterAnimAvis opened this issue Apr 16, 2024 · 1 comment · Fixed by #173
Closed

Add handling for pom dependencies #144

AterAnimAvis opened this issue Apr 16, 2024 · 1 comment · Fixed by #173
Labels
bug Something isn't working

Comments

@AterAnimAvis
Copy link
Contributor

When adding a dependency on something like https://mvnrepository.com/artifact/org.graalvm.polyglot/python/23.1.2, Gradle will resolve this to the pom and pull in it's dependencies transitively.

Resolving the dependency directly will result in the .pom file, UnionFileSystem expects entries to be a zip/jar/directory, adding the pom resulting in ProviderNotFoundExceptions in UnionFileSystem#openFileSystem at runtime.

Originally from Discord
@sciwhiz12 sciwhiz12 added the bug Something isn't working label Apr 18, 2024
@marchermans
Copy link
Contributor

Can I get an example for this, so that I can write a unit test and debug it?

marchermans added a commit that referenced this issue May 16, 2024
@marchermans
Only allow directories, jars and zips on the lcp.
1d0e313 
Closes: #144
@marchermans marchermans mentioned this issue May 16, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Tech-Debt] Switch to using full named configurations. neoforged/NeoGradle
3 participants
@marchermans @AterAnimAvis @sciwhiz12