-
-
Notifications
You must be signed in to change notification settings - Fork 731
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
Chocolatey package dependencies cannot be set using the ChocolateyPackSettings #1943
Comments
So... I was looking at implementing this so I could submit a PR. The implementation is easy, but I am having difficulty working out how to unit test the change. It looks as if the unit tests are based on the abstract ChocolateyFixture (by way of the ChocolateyPackerFixture), but neither the ChocolateyPackerWithNuSpecFixture or the ChocolateyPackerWithoutNuSpecFixture currently appear to contain any test assertions at all. Am I looking in the right place? |
@RichardJFoster The Chocolatey Pack tests are here: Seems like you are looking in the Fixtures folder, which contains the setup logic for running the actual tests. |
If you look at this file: You will find the where the dependencies are tested in the NuGet version. |
Aha! Excellent. I was looking in the wrong place. :-) Thanks for the pointers. |
@RichardJFoster you are very welcome! Let us know if you have any questions! |
No questions for now. Just waiting on the contribution license email, but if there are comments on the PR in the mean time I'm all ears. :-) |
GH1943: Allow ChocolateyPackSettings to specify dependent packages
Fixed by #1945 |
This problem affects Cake 0.23.0
The ChocolateyPackSettings class does not contain any mechanism to add package dependencies.
The expected operation is that the ChocolateyPackSettings has a Dependencies property that mirrors the Dependencies property already present in the NuGetPackSettings.
This problem was first observed on a 64 bit Windows system, but an examination of the source suggests this issue is not dependent on OS or build server type.
The text was updated successfully, but these errors were encountered: