-
Notifications
You must be signed in to change notification settings - Fork 15
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 the generated project build capability #200
Improve the generated project build capability #200
Conversation
3814c67
to
02b7a42
Compare
README.md
Outdated
@@ -31,6 +31,10 @@ export https_proxy=http://localhost:3128 | |||
``` | |||
Symphony Generator will automatically fetch the latest version of BDKs/WDK and use it to generate your project. In case the request fails, it will fallback on a default version. | |||
|
|||
Once the project is generated, the generator will try to download the chosen package manager wrapper to build the project, if for any reason (e.g. network constraint) the build fails, the generator will then try to build project again by using local package manager. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can improve this line IMO. Let's mention it is specific to BDK Java bots.
Once the project is generated, the generator will try to download the chosen package manager wrapper to build the project, if for any reason (e.g. network constraint) the build fails, the generator will then try to build project again by using local package manager. | |
In case of a Java bot application, once the project is generated, the generator will try to download the chosen package manager wrapper to build it. If for any reason (e.g. network constraint) the build fails, the generator will then try to build the project again by using local package manager. |
this.spawnCommandSync('gradle', ['build']); | ||
} catch(e) { | ||
this.log(`${e}`.green.bold); | ||
console.log(errorMessage); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it done on purpose to not show the actual error? only "Failed to build the generated project?".
How can users figure out why the generation failed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the actual error is shown by the line 209. The error message is a generic message.
and as i mentioned this morning, the real error message will display by all means.
02b7a42
to
ddfb10d
Compare
Before this commit, the generation process would stop in case the build on the generated project fails. For instance, the package manager wrapper cannot be downloaded due to network issue. This commit improves the project build capability by tring to run a the build again by using a local package manager in case there is an issue when build fails using wrapper. In addition, no matter what the build status is, the generation process will continue to the end.
ddfb10d
to
6d27087
Compare
Before this commit, the generation process would stop in case the build
on the generated project fails. For instance, the package manager wrapper
cannot be downloaded due to network issue.
This commit improves the project build capability by tring to run
a the build again by using a local package manager in case there is an
issue when build fails using wrapper. In addition, no matter what the build
status is, the generation process will continue to the end.
Description
Closes #199