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

Custom Maven Transport for NuGet #44

Open
wasabii opened this issue Dec 3, 2023 · 0 comments
Open

Custom Maven Transport for NuGet #44

wasabii opened this issue Dec 3, 2023 · 0 comments

Comments

@wasabii
Copy link
Collaborator

wasabii commented Dec 3, 2023

The way we load .pom files embedded into NuGet packages isn't quite right. We incorporate the dependencies mentioned directly as MavenReferenceItems, with the exact same scope, for the dependending project. This means we don't consider the NuGet packages, or ProjectReferences, within the Maven resolution logic.

So, since we don't treat NuGet packages as actual Maven projects to traverse through, the .pom files located in NuGet packages can't do much more than declare dependencies. No custom repositories, etc.

How we might solve this.... custom Maven transport, implementing ikvm.nuget: protocol, and ikvm.project: protocol. Which fictionalize results as if the including ProjectReferences and/or non-transitive PackageReferences were actual Maven projects with fake POM files that declare their dependencies. Would allow Maven to traverse through them naturally.

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

No branches or pull requests

1 participant