Project references are not converted to Nuget Dependencies
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
Project PackageB with a dependency on the project PackageA where both projects have a paket.template and the packages use paket pack with the --include-referenced-projects flag should have a Nuget dependency on PackageA but does not.
Paket automatically replaces inter-project dependencies with NuGet dependencies if the dependency has it's own paket.template. In addition to this the parameter --include-referenced-projects instructs Paket to add project output to the package for inter-project dependencies that don't have a paket.template file.
Repro steps
Here is the raw paket command:
C:\Projects\demo\.paket\paket.exe pack output "../../artifacts" --build-config Release --template C:\Projects\demo\src\PaketDemo.PackageB\paket.template --symbols --minimum-from-lock-file --verbose --include-referenced-projects
Here is a project which reproduces the issue:
https://github.com/Lavinski/paket-demo
Expected behavior
ProjectB should have a dependency on ProjectA
Actual behavior
Project references are not reflected in the resulting package.
Known workarounds
None
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the raw paket pack command and the linked paket-demo reproduction, then inspect how the generated package metadata represents the PackageB to PackageA project reference. Confirm the behavior with both projects' paket.template files and --include-referenced-projects; done means the resulting PackageB package declares PackageA as a NuGet dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100