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
{{ message }}
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.
After copying the source projects to the target location.
Do the k build on the source projects to generate the nupkg for each. Source packages should be built innermost-first from a dependency standpoint.
Expand those newly built nupkgs into the target packages folder. These expanded packages must be favored over the source project when calculating dependency versions.
The text was updated successfully, but these errors were encountered:
@glennc this is one of the two features we just talked about, actual implementation may be different than what is described, but in general it's the ability for a source project in the input to kpm pack becomes a package project in the output
After copying the source projects to the target location.
Do the
k build
on the source projects to generate the nupkg for each. Source packages should be built innermost-first from a dependency standpoint.Expand those newly built nupkgs into the target packages folder. These expanded packages must be favored over the source project when calculating dependency versions.
The text was updated successfully, but these errors were encountered: