User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.63 Safari/537.31 Build Identifier: When using zanata-cli to pull from server and encounter an error, the output will hint:[ERROR] Use -e/--errors for full stack trace (or when reporting bugs) And the help output will also contain these options for detail error stacktrace. But specifying -e/--errors and/or -X/--debug will give no effect and user won't see any stacktrace nor root cause of error. Reproducible: Always Steps to Reproduce: 1. Get a copy of zanata server without rhbz1002774. i.e. server version 3.0.2 2. Use client version 3.1.1 3. Push a plural text flow 4. Translate the plural text flow 5. On the client change the plural text flow back to singular form 6. Push again 7. On server verify the text flow in editor has now become singular and become fuzzy. Save that entry to translated. 8. Pull again with option -e or -X Actual Results: Getting an error because of the inconsistent plural form but no detail cause. [ERROR] Execution failed: Operation failed. Expected Results: See the actual exception message. maven client is fine. It's only the java client. You can get a java client from maven or build client from source and there should be a tar/zip dist under target
moving the -e or -X before the subcommand will work. So this is not technically a bug. It's just not user friendly.
Well, it is a bug, because the subcommands do list -e and -X in their help messages, which implies that they should recognise them. And if they don't recognise them, they should say so instead of failing silently. But it is a bug with a workaround.
*** Bug 1030139 has been marked as a duplicate of this bug. ***
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-284