Bug 727406

Summary:	Maven client 1.4 failed to push to Zanata 1.3.1 if -Dzanata.pushTrans is given
Product:	[Retired] Zanata	Reporter:	Ding-Yi Chen <dchen>
Component:	Component-Maven	Assignee:	zanata-dev-internal <zanata-dev-internal>
Status:	CLOSED NOTABUG	QA Contact:	Ding-Yi Chen <dchen>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	1.3-alpha-3	CC:	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:	2011-08-02 05:52:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ding-Yi Chen 2011-08-02 04:26:02 UTC

Description of problem:
When zanata maven client 1.4-SNAPSHOT failed to push to Zanata 1.3.1 Server if 
 -Dzanata.pushTrans is given.

Version-Release number of selected component (if applicable):
[INFO] client API version: 1.4-SNAPSHOT, server API version: 1.3.1-SNAPSHOT
[WARNING] client API version is 1.4-SNAPSHOT, but server API version is 1.3.1-SNAPSHOT

How reproducible:
Always

Steps to Reproduce:
0. Assume the document, AboutFedora, is ready in the client, and enable locale jp.
1. Create project: AboutFedora
2. Create version: f11
3. mvn -e -B org.zanata:zanata-maven-plugin:push -Dzanata.url=http://ZanataServer.org  -Dzanata.projectType=podir  -Dzanata.pushTrans
  
Actual results:
[ERROR] Failed to execute goal org.zanata:zanata-maven-plugin:1.4-SNAPSHOT:push (default-cli) on project null: Zanata mojo exception: operation returned 400 (Bad Request): Unsupported Locale: ja within this context. Please contact Admin., uri: http://flies-devel.englab.bne.redhat.com/rest/projects/p/AboutFedora/iterations/i/f11/r, annotations: [@javax.ws.rs.PUT(), @javax.ws.rs.Path(value={id}/translations/{locale})] -> [Help 1]


Expected results:
Proceed without error.

Comment 1 Ding-Yi Chen 2011-08-02 05:52:18 UTC

It turns that I was looking on different server, thus, this bug report is not valid.