Bug 727406 - Maven client 1.4 failed to push to Zanata 1.3.1 if -Dzanata.pushTrans is given
Maven client 1.4 failed to push to Zanata 1.3.1 if -Dzanata.pushTrans is given
Product: Zanata
Classification: Community
Component: Component-Maven (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: zanata-dev-internal
Ding-Yi Chen
Depends On:
  Show dependency treegraph
Reported: 2011-08-02 00:26 EDT by Ding-Yi Chen
Modified: 2011-09-11 20:36 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-08-02 01:52:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ding-Yi Chen 2011-08-02 00:26:02 EDT
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:

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 01:52:18 EDT
It turns that I was looking on different server, thus, this bug report is not valid.

Note You need to log in before you can comment on or make changes to this bug.