Skip to content

Commit

Permalink
Update README with more local development options (#351)
Browse files Browse the repository at this point in the history
  • Loading branch information
tiagobento authored Dec 10, 2020
1 parent 290be83 commit 13a88b9
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -78,6 +78,17 @@ Develop
--------------------
> **NOTE:** We recommend using *LTS* version of Node.js when developing this project. Our CI uses Node `12.16.3` and Yarn `1.19.1`.
> **NOTE:** This repo now consumes NPM packages containing the exploded WARs of the BPMN, DMN, and SceSim Editors. For this reason, if you want to use a local build of one of them during development, you can use some environment variables to point to the exploded WAR directories.
> - BPMN: `EXTERNAL_RESOURCE_PATH__bpmnEditor`
> - DMN: `EXTERNAL_RESOURCE_PATH__dmnEditor`
> - SceSim: `EXTERNAL_RESOURCE_PATH__scesimEditor`
>
> **Example:**
>
> $ export EXTERNAL_RESOURCE_PATH__bpmnEditor=/Users/tiago/redhat/kie-wb-common/kie-wb-common-stunner/kie-wb-common-stunner-sets/kie-wb-common-stunner-bpmn/kie-wb-common-stunner-bpmn-kogito-runtime/target/kie-wb-common-stunner-bpmn-kogito-runtime
>
> $ yarn run init && yarn run build:prod
##### VS Code Extension
1. After you've successfully built the project following the instructions above, open the `packages/vscode-extension-pack-kogito-kie-editors` folder on VS Code. Use a new VS Code window so that the `packages/vscode-extension-pack-kogito-kie-editors` folder shows up as root in the VS Code explorer.
Expand Down

0 comments on commit 13a88b9

Please sign in to comment.