Red Hat Bugzilla – Bug 987823
Do not ship the Playground repo
Last modified: 2014-08-06 16:15:52 EDT
At the moment, kie-ide has a hardcoded playground Git project. There is a wide agreement that we shouldn't ship any such repository, so I kindly ask for this to be removed in the productized version.
Load of playground repos has been disabled by default (only for hosted mode and jbpm installer it is enabled). Here are commits for this change:
When running on application server it can be easily enabled by setting system property as follows:
- for jbpm console use: -Dorg.jbpm.console.demo=true
- for kie-wb use: -Dorg.kie.wb.demo=true
- for kie-drools-wb use: -Dorg.kie.droolswb.demo=true
Since that disables both Group and Repository load it means there will be nothing available (from authoring point of view) when application starts, to setup initial group/repository kie-config-cli tool can be used to bootstrap system repository.
based on discussion slight change was applied to make the playground enabled by default with possibility to disable it via system property. In addition property names were unified to single one:
To disable it set system property to false:
that will disable completely playground repository load.
Created attachment 786758 [details]
I tried this on "sync.2013.08.07".
I added system property -Dorg.kie.demo=false, but the playground is still installed.
Attached standalone.sh and server.log.
Move to Assigned status for investigation.
Created attachment 786759 [details]
Ryan, did you remove .niogit folder from previous installations? As it might be it is still present there so kie-wb does not need to load it from remote and just uses what has already been there.
Yes, I tried with removing .niogit folder and the jbpm-playground still appeared.
And beside this, for requirement of the product, we can't modifiy the standalone.sh of EAP.
May I suggest that we keep this option inside the war.
For example, we have an properties.file inside the kie-wb.war that we can patch easily from "false" to "true".
Repo is still shipped in ER2, but is disabled by default. Since this is the intended behavior, VERIFIED.