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

Report broken project dependencies properly #2131

Merged
merged 1 commit into from Jan 30, 2017

Conversation

Projects
None yet
2 participants
@vivainio

vivainio commented Jan 30, 2017

Currently, if there are broken project dependencies, Paket just says "Unable to parse: something.csproj". It doesn't specify what project has the broken reference, or that there are broken project dependencies in the first place.

This new warning specifies what csproj you need to fix, and that we are indeed dealing with broken project dependencien.

Ville M. Vainio
@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Jan 30, 2017

Member

thanks!

Member

forki commented Jan 30, 2017

thanks!

@forki forki merged commit 0612a1f into fsprojects:master Jan 30, 2017

1 of 2 checks passed

continuous-integration/travis-ci/pr The Travis CI build failed
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment