fsprojects / fsprojects/Paket

Packages created with paket.template type "project" do not include dependencies to projects with paket.template type "files"

Open
#4,121 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
F#
Stars
2.1k
Forks
528
Avg merge
1d 12m
Merged PRs (30d)
54

Description

Description

paket.template files with type "project" do not include references to projects with paket.template files of type "files"

The documentation says

including project references for projects in the solution that have a paket.template file.

https://fsprojects.github.io/Paket/template-files.html

paket version 6.2.1

Repro steps

Create project A with paket.template file type files
Create project B with paket.template file type project
Let B project reference project A
Call paket pack

project A

type file
id A
version 1.0.0.0
authors XXX
description
  A
files
	..\..\Build\Repacked\A.dll ==> lib\net472
dependencies 
  Test LOCKEDVERSION
excludeddependencies
  Microsoft.CodeAnalysis.FxCopAnalyzers
  StyleCop.Analyzers

project B

type project
id B
version 1.0.0.0
authors XXX
description
  B
excludeddependencies
  Microsoft.CodeAnalysis.FxCopAnalyzers
  StyleCop.Analyzers
Expected behavior

NuGet package of B has a dependency to NuGet package A.

Actual behavior

NuGet package B has no dependency to A

Known workarounds

Change all paket.template files of type projec to type files :(

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with the two paket.template files described in the report and run paket pack. Compare the generated NuGet package dependencies for project B with the expected dependency on project A; done means the project reference is included when A uses type files and B uses type project.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.