commit | 07314ef7117ceba1fa556275f78cbe11337e4b38 | [log] [tgz] |
---|---|---|
author | Paulo Martins <paulovmr@gmail.com> | Mon Dec 09 14:23:53 2019 -0300 |
committer | Paulo Martins <paulovmr@gmail.com> | Mon Dec 09 14:23:53 2019 -0300 |
tree | bb8fea553b908d6de6168206095f8d822940e3c9 | |
parent | 8023ac66693759eed90dc0e7a0ce2f4fb75727f5 [diff] |
unpacked editors
Kogito is the next generation of business automation platform focused on cloud-native development, deployment and execution.
Homepage: http://kogito.kie.org
Wiki: https://github.com/kiegroup/kogito-tooling/wiki
JIRA: https://issues.jboss.org/projects/KOGITO
jBPM: https://www.jbpm.org/
Drools: https://www.drools.org/
This module contains a number of examples that you can take a look at and try out yourself. Please take a look at the readme of each individual example for more details on how the example works and how to run it yourself (either locally or on Kubernetes):
In Kogito Tooling releases page you will find extensions and released tooling packages.
Check out the source:
git clone git@github.com:kiegroup/kogito-tooling.git
If you don't have a GitHub account use this command instead:
git clone https://github.com/kiegroup/kogito-tooling.git
Build with Yarn:
cd kogito-tooling yarn run init #prod yarn run build:prod # dev yarn run build # skips integration tests and production packing yarn run build:fast # skips lint and unit tests
Final artifacts will be on
packages/*/dist
directories.
NOTE: We currently pack two GWT-based editors -- BPMN and DMN. They are exploded WARs, so we don‘t commit them in this repo. We are currently working on automatically fetching them during the build, but we didn’t do it yet. For builds to work properly, you must have the exploded WARs copied on
packages/kie-bc-editors-unpacked/
dmn
andbpmn
folders. You can go to the latest commit, click on the “check” icon and download the exploded WARs from the Artifacts tab. Be aware that each editor must go on its own folder.
packages/vscode-extension-pack-kogito-kie-editors
folder on VSCode. Use a new VSCode window so that the packages/vscode-extension-pack-kogito-kie-editors
folder shows up as root in the VSCode explorer.Debug
menu/section. You can also use the respective shortcuts (F5 to start debugging, for instance).packages/vscode-extension-pack-kogito-kie-editors
, you have to manually rebuild them before relaunching the extension on VSCode.packages/chrome-extension-pack-kogito-kie-editors
folder on your favourite IDE. You can import the entire repo as well if you want to make changes to other packages.yarn run serve-envelope
on packages/chrome-extension-pack-kogito-kie-editors
. This will start a webpack-dev-server
instance with the editors and their envelope. We use that because we don't pack the Chrome Extension bundle with the editors inside. Instead, we fetch them from GitHub pages.chrome://extensions
. Enable “Developer mode” on the top right corner and click on “Load unpacked”. Choose the packages/chrome-extension-pack-kogito-kie-editors/dist
folder.All contributions are welcome! Before you start please read the Developing Drools and jBPM guide.
Here are some of the most notable ones for quick reference: