Guest User

Untitled

a guest
Apr 16th, 2019
180
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.05 KB | None | 0 0
  1. Modified files: ./edge-developer-training-backend/edge.json
  2. [[INFO] Scanning for projects...
  3. INFO] Scanning for projects...
  4. [INFO] ----------------------------------[---INF--O] ---------------------------------------------------------------------------------
  5. [INFO] BUILD FAILURE
  6. [INFO] ------------------------------------------------------------------------
  7. ------------------------
  8. [INFO] BUILD FAILURE
  9. [INFO] ------------------------------------------------------------------------
  10. [[INFO] Total timINFO] Total time: 0.328 s
  11. [INFO] 28 s
  12. Finished at: 2019-04-17T04:58:51+03:00
  13. [INFO] ------------------------------------------------------------------------
  14. [INFO] Finished at: 2019-04-17T04:58:51+03:00
  15. [INFO] ------------------------------------------------------------------------
  16. [[ERROR] NERROR] No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:o goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1]
  17. [ERROR]
  18. [ERROR] To see the full stack trace of the errors, re-run Maven wit<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1]
  19. [ERROR]
  20. [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
  21. [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  22. [ERROR]
  23. [ERROR] For more information about the errors and possible solutions, please read the following articles:
  24. [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoGoalSpecifiedException
  25. h the -e switch.
  26. [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  27. [ERROR]
  28. [ERROR] For more information about the errors and possible solutions, please read the following articles:
  29. [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoGoalSpecifiedException
  30. "6006" �� ���� ����७��� ��� ���譥�
  31. ��������, �ᯮ��塞�� �ணࠬ��� ��� ������ 䠩���.
  32. (node:11272) UnhandledPromiseRejectionWarning: #<Object>
  33. (node:11272) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
  34. (node:11272) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
  35. "6006" �� ���� ����७��� ��� ���譥�
  36. ��������, �ᯮ��塞�� �ணࠬ��� ��� ������ 䠩���.
  37. (node:11272) UnhandledPromiseRejectionWarning: #<Object>
  38. (node:11272) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
Advertisement
Add Comment
Please, Sign In to add comment