Bug 1030151

Summary:	zanata-cli: Error message should not mention Maven
Product:	[Retired] Zanata	Reporter:	David Mason <damason>
Component:	Component-zanata-client	Assignee:	Damian Jansen <djansen>
Status:	CLOSED UPSTREAM	QA Contact:	Zanata-QA Mailling List <zanata-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	development	CC:	dchen, sflaniga, zanata-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-29 03:29:33 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 David Mason 2013-11-14 02:57:18 UTC

Description of problem:
When running a push or pull with zanata-cli in a Jenkins job, if batch mode is not specified there is an error when user input is required. The error text mentions Maven, but zanata-cli is not run from Maven.


Version-Release number of selected component (if applicable):


How reproducible:
Moderate, always


Steps to Reproduce:
1. Create a jenkins task that runs zanata-cli pull
2. Run the jenkins task
3. View console output

Actual results:
Output includes the line:
[ERROR] Execution failed: console not available: please run Maven from a console, or use batch mode option (-B)


Expected results:
[ERROR] Execution failed: console not available: please run zanata-cli from a console, or add batch mode option (-B) before the sub-command

Additional info:

Comment 2 Sean Flanigan 2013-11-14 04:53:02 UTC

How about this for Expected results? :

[ERROR] Execution failed: console not available: please run the client from a console, or use batch mode option (-B).

I'd rather we fixed zanata-cli so that the help didn't suggest -B was allowed after the subcommand, than go to the trouble of customising this error message for Maven vs zanata-cli.

Comment 3 Zanata Migrator 2015-07-29 03:29:33 UTC

Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-293