agrz opened a new issue, #1800: URL: https://github.com/apache/incubator-kie-issues/issues/1800
Hi, recently a very strange error started to occur in the Kogito 10 release BPMN Editor that worked quite fine before. I know there are plans to replace the wid mechanism with something else, but in the current v10 this is still the way to use custom task elements in the editor and needed for any extension to be used in BPMN. This worked until recently with the same version of the Kogito plugin. **Environment:** Mac OS 15.2 VSCode 1.96.4 Kogito Extension Bundle Version 10 Reproducible on multiple different machines Same behavior is also reproducible with older versions of the Kogito Extension **Description** The loading of custom workitem definitions from the global folder is no longer working in the vscode plugin if there is a .git folder in the opened project root. **Steps to reproduce** - Have a git repository cloned to the local file system (i.e. see sample repo I created: https://github.com/newwork-software/kogito-bpmn-editor-error) - Have a global folder with a .wid file (i.e. RestWorkItem from [Kogito examples](https://github.com/apache/incubator-kie-kogito-examples/blob/741a4a2b3b03dbbfb326a710e49f162d47a49dbe/kogito-quarkus-examples/process-rest-workitem-multi-quarkus/src/main/resources/RestWorkDefinition.wid) ) - In VSCode use open folder and select the cloned repository - Open a bpmn process file in the Kogito BPMN extension (src/main/resources/numbers.bpmn) - Click on the custom task palete icon (cog symbol) **Expected result** The Rest workitem shows in the custom tasks.  **Actual result** The custom tasks only show the milestone task but with only a dummy icon.  If you go into the .git folder and rename the index file to index_ then close and reopen the bpmn editor, the custom task shows as expected. Same if you open a project without a .git folder. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
