Bug 1000592

Summary:	Provide the user with an information message why 'build&deploy' failed.
Product:	[Retired] JBoss BRMS Platform 6	Reporter:	Marek Baluch <mbaluch>
Component:	Business Central	Assignee:	Maciej Swiderski <mswiders>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Marek Baluch <mbaluch>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	mswiders, rzhang
Target Milestone:	ER3	Flags:	manstis: needinfo+
Target Release:	6.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	BRMS/BPMS 6.0.0.ER1
Last Closed:	2014-08-06 20:16:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Marek Baluch 2013-08-23 19:21:25 UTC

Description of problem:

When a user tries to 'build&deploy' a project he can see two messages:
1) build successfull
2) build failed.

If the second one occurs the user receives zero information why the build failed and therefor is left clueless what he did wrong.

Comment 1 manstis 2013-08-27 08:18:48 UTC

If the build failed the "Problems Panel" should be opened containing details of errors in the build. Can you confirm this?

Comment 2 Maciej Swiderski 2013-08-27 12:48:22 UTC

Mike, I'll take this and apply same approach for deployment to show info/error messages for deployments that are runtime specific - not maven artifact deployments.

Comment 3 Maciej Swiderski 2013-08-28 12:48:03 UTC

Deployment to runtime will now report errors on Problems Panel during build and deploy and in case of failure the build will display failure notification as well.

In addition Deployments panel of BPMS has been enhanced to include Problems Panel so when you manually deploy kjars failures will be reported there as well.

Guvnor commit:
https://github.com/droolsjbpm/guvnor/commit/98d61832abe900efb75cba5ea7497f63fe175573

jbpm console commit:
https://github.com/droolsjbpm/jbpm-console-ng/commit/0100de16430d56577ce70305bb1d2e708cca5aa4

Comment 4 Marek Baluch 2013-09-19 15:06:44 UTC

Verified on ER3.

When for e.g. the process contains validation issues these can be seen in the 'Problems View'. If for example the artifact id is not valid then a new dialog will inform about it.