Hide Forgot
Created attachment 577226 [details] Maven client log Description of problem: It looks like maven can no longer push with -Dzanata.pushTrans Version-Release number of selected component (if applicable): client API version: 1.6-SNAPSHOT, server API version: 1.6-SNAPSHOT [WARNING] client API timestamp is 20120412-1426, but server API timestamp is 20120413-0001 How reproducible: Quite a lot of time Steps to Reproduce: 1. Server enable locale ja 2. Project/Version to be pushed "AboutFedora/f13" 3. edit zanata.xml as follows: <config xmlns="http://zanata.org/namespace/config/"> <url>SERVERURL</url> <project>AboutFedora</project> <project-version>f13</project-version> <project-type>podir</project-type> <locales> <locale map-from="ja-JP">ja</locale> </locales> </config> 4. mvn -e zanata:push -B -Dzanata.pushTrans Actual results: [ERROR] Failed to execute goal org.zanata:zanata-maven-plugin:1.6-SNAPSHOT:push (default-cli) on project null: Zanata mojo exception: operation returned 400 (Bad Request): empty TextFlowTarget 6bb2aaa48c3a478925800ff269953856 must have ContentState New, uri: http://zanata-empire.lab.eng.bne.redhat.com:8080/rest/projects/p/UserGuide/iterations/i/f14/r, annotations: [@javax.ws.rs.PUT(), @javax.ws.rs.Path(value={id}/translations/{locale})] -> [Help 1] See attached client.log and server.log for details. Expected results: Translation pushed without error Additional info: Python client seems working fine.
Could you please attach the PO file you were using?
Created attachment 577237 [details] Server log
Created attachment 577238 [details] Source pot
Created attachment 577239 [details] Translation to be pushed with pushTrans
Changed the way the PO file reader determines the state of a translation unit based on its content(s). See: https://github.com/zanata/zanata/commit/54df7f5c29b121cbb39ceb6c58ac2e6ba405080b
This should be fixed now, but note bug 814006 concerning plural forms and invalid PO files.
verified with maven client 1.6.0-alpha-3-SNAPSHOT