Activity
Show:
Former user
changed the Status5 October 2017 at 05:28Open
Closed
Former user
updated the Resolution5 October 2017 at 05:28None
Duplicate
Former user
updated the Link5 October 2017 at 05:28None
This issue duplicates ZNTA-1327
Former user
updated the Rank28 March 2017 at 23:16None
Ranked higher
Former user
updated the Description21 March 2017 at 01:08If there is no zanata.xml and we pass all information from command line, zanata client failed to load locales from server.
How to reproduce:
Just go to a folder without zanata.xml, then run something like:
zanata-cli -e pull --trans-dir /tmp/trans --username tester --key key --project project --project-version master --project-type podir --url http://localhost:8080/
What you get:
{code}
[ERROR] Execution failed:
org.zanata.client.exceptions.ConfigException: no locales specified
at org.zanata.client.commands.pull.PullCommand.run(PullCommand.java:149)
{code}
What's expected:
It should load locales from the server and continue
If there is no zanata.xml and we pass all information from command line, zanata client failed to load locales from server.
How to reproduce:
Just go to a folder without zanata.xml, then run something like:
zanata-cli -e pull --trans-dir /tmp/trans --username tester --key key --project project --project-version master --project-type podir --url http://localhost:8080/
What you get:
{code}
[ERROR] Execution failed:
org.zanata.client.exceptions.ConfigException: no locales specified
at org.zanata.client.commands.pull.PullCommand.run(PullCommand.java:149)
{code}
What's expected:
It should load locales from the server and continue
In addition:
When you do provide --locales from command line, it results in:
{code}
java.lang.NullPointerException
at org.zanata.client.commands.PushPullCommand.getLocaleMapList(PushPullCommand.java:202)
at org.zanata.client.commands.AbstractPushPullOptionsImpl.getLocaleMapList(AbstractPushPullOptionsImpl.java:63)
{code}
Former user
updated the Rank21 March 2017 at 01:05None
Ranked higher
Sean Flanigan
created the Issue1 February 2017 at 06:28Something went wrong on our end
If this keeps happening, share this information with your admin, who should contact support.
Hash OWEI1K
Trace 5ae17452d87b4f52934526b89ab9f92c
Details
Details
Assignee
Reporter
Tested Version/s
None
Components
Priority
