Skip to content
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

Improve error messaging for apps containing multiple projects #809

Open
fg-j opened this issue Oct 17, 2022 · 0 comments
Open

Improve error messaging for apps containing multiple projects #809

fg-j opened this issue Oct 17, 2022 · 0 comments

Comments

@fg-j
Copy link

fg-j commented Oct 17, 2022

Describe the Enhancement

It's a common pattern in .NET apps for one "app" to contain several projects. Like this test fixture. Often, when users first attempt to build these apps with buildpacks, they struggle to correctly use BP_DOTNET_PROJECT_PATH and set the build context for their build (e.g. with pack build myimage --path to/src). Users may mistakenly:

  • not set BP_DOTNET_PROJECT_PATH, making it ambiguous which project they wish to build
  • set BP_DOTNET_PROJECT_PATH to the wrong proj file
  • limit the build context to only one project that contains references to other projects.

It would be a better user experience if the buildpack provides better advice to users about whether to adjust their build context and/or change the value of BP_DOTNET_PROJECT_PATH.

Possible Solution

Motivation

@fg-j fg-j moved this to ❓Not scoped in Paketo Workstreams Oct 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Not scoped
Development

No branches or pull requests

1 participant