Bug 865668 - mvn zanata:push -Dzanata.pushType=trans tries to delete obsolete source documents
Summary: mvn zanata:push -Dzanata.pushType=trans tries to delete obsolete source docum...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: Component-Maven
Version: 1.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 2.0
Assignee: Sean Flanigan
QA Contact: Ding-Yi Chen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-12 05:25 UTC by Sean Flanigan
Modified: 2013-02-27 08:10 UTC (History)
2 users (show)

Fixed In Version: 1.7.4-SNAPSHOT (20121019-0015)
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-02-27 08:10:24 UTC
Embargoed:

Attachments (Terms of Use)

Description Sean Flanigan 2012-10-12 05:25:50 UTC 
Description of problem:
Client attempts to delete source documents when pushType is "translations only".

Version-Release number of selected component (if applicable):
1.7.1

How reproducible:
100%

Steps to Reproduce:
1. Create a source document, push to zanata
2. Delete source document
3. mvn zanata:push -Dzanata.pushType=trans
  
Actual results:
Deletes document from server if user has required security permissions (project maintainer/admin).  Otherwise, a 401 error is returned.

Expected results:
Any other documents pushed, obsolete document ignored.
Comment 2 Sean Flanigan 2012-10-12 06:44:51 UTC 
Fixed in release (client 1.7.4-SNAPSHOT): https://github.com/zanata/zanata-client/commit/0bfdb2f46bca63cb79bd4482fd3ca8ed49addb48

In integration/master (client 1.8.0-SNAPSHOT): https://github.com/zanata/zanata-client/commit/67adb17600fa6537178763c92b0c07f867544a31
Comment 6 Ding-Yi Chen 2012-10-19 08:15:53 UTC 
VERIFIED with 
[INFO] client API version: 1.8.0-SNAPSHOT, server API version: 1.8.0-SNAPSHOT
on Zanata version 1.8.0-SNAPSHOT (20121019-0031)


client API version is 1.7,2, but server API version is 1.7.1-SNAPSHOT 
on Zanata version 1.7.4-SNAPSHOT (20121019-0015)
Note You need to log in before you can comment on or make changes to this bug.