*** Description of problem: When the deployment fails. An exception like the following one is present in the server log then an artifact is created in the repository. 11:01:42,949 ERROR [stderr] (http-/127.0.0.1:8080-4) java.lang.NullPointerException 11:01:42,950 ERROR [stderr] (http-/127.0.0.1:8080-4) at org.jbpm.kie.services.impl.KModuleDeploymentService.deploy(KModuleDeploymentService.java:68) 11:01:42,950 ERROR [stderr] (http-/127.0.0.1:8080-4) at org.jbpm.kie.services.impl.KModuleDeploymentService$Proxy$_$$_WeldClientProxy.deploy(KModuleDeploymentService$Proxy$_$$_WeldClientProxy.java) 11:01:42,951 ERROR [stderr] (http-/127.0.0.1:8080-4) at org.jbpm.console.ng.bd.backend.server.DeploymentManagerEntryPointImpl.deploy(DeploymentManagerEntryPointImpl.java:77) 11:01:42,951 ERROR [stderr] (http-/127.0.0.1:8080-4) at org.jbpm.console.ng.bd.backend.server.DeploymentManagerEntryPointImpl.autoDeploy(DeploymentManagerEntryPointImpl.java:165) 11:01:42,952 ERROR [stderr] (http-/127.0.0.1:8080-4) at org.jbpm.console.ng.bd.backend.server.DeploymentManagerEntryPointImpl$Proxy$_$$_WeldClientProxy.autoDeploy(DeploymentManagerEntryPointImpl$Proxy$_$$_WeldClientProxy.java) *** How reproducible: Steps to Reproduce: 1) Create a new project (e.g. in jbpm-playground.git) 2) Hit the "Build & Deploy" button 3) Check the repository. *** Actual results: Jar file present in the repository. *** Expected results: No file in the repository (or an older version) if the deployment failed.
Fixed in master
Verified on DR6.