You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: