[zanata-bugs] [Bug 805775] New: confusing error: failed to upload glossary due to wrong an API key

bugzilla at redhat.com bugzilla at redhat.com
Thu Mar 22 05:21:04 UTC 2012


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: confusing error: failed to upload glossary due to wrong an API key

https://bugzilla.redhat.com/show_bug.cgi?id=805775

           Summary: confusing error: failed to upload glossary due to
                    wrong an API key
           Product: Zanata
           Version: 1.6-SNAPSHOT
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: high
          Priority: unspecified
         Component: Usability
        AssignedTo: runab at redhat.com
        ReportedBy: jochang at redhat.com
         QAContact: dchen at redhat.com
                CC: zanata-bugs at redhat.com
   Estimated Hours: 0.0
    Classification: Community
      Story Points: ---
              Type: ---
        Regression: ---
        Mount Type: ---
     Documentation: ---


Description of problem:
when pushing glossary to Zanata with an wrong API key,it will result in build
failure. The return error should specify a statement to help users by
clarifying error such as  "unable to authenticate users,maybe API key is
wrong".   

How reproducible:
always

Steps to Reproduce:
1.go to the folder where the glossary file(.po) is located.
2.open terminal 
3.issue command $mvn zanata:glossary-push
4.BUILD FAILURE is shown on the screen

Actual results:

error as below:

Failed to execute goal
org.zanata:zanata-maven-plugin:1.6-SNAPSHOT:glossary-push (default-cli) on
project null: Zanata mojo exception: Could not find JAXBContextFinder for media
type: text/html;charset="ISO-8859-1" -> 


Expected results:

error as below:

unable to authenticate users,maybe API key is wrong

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.




More information about the zanata-bugs mailing list