Bug 1030231 - Misleading error message when if one of the zanata.ini entries contains invalid URL
Misleading error message when if one of the zanata.ini entries contains inval...
Status: CLOSED WONTFIX
Product: Zanata
Classification: Community
Component: Component-Maven (Show other bugs)
3.1
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Damian Jansen
Zanata-QA Mailling List
: screened
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-14 03:29 EST by Ding-Yi Chen
Modified: 2015-03-22 22:34 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-03-22 22:34:18 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ding-Yi Chen 2013-11-14 03:29:35 EST
Description of problem:
If one of the zanata.ini entries contains invalid URL, running maven client return following error message:

[ERROR] Failed to execute goal org.zanata:zanata-maven-plugin:3.1.2:push (default-cli) on project standalone-pom: Zanata mojo exception: 'SERVER1..url' doesn't map to a class java.net.URL: The value  can't be converted to an URL: no protocol: -> [Help 1]

Version-Release number of selected component (if applicable):
zanata-maven-plugin:3.1.2

How reproducible:
Always with following zanata.ini


# Start zanata.ini
[servers]
SERVER1.url = 
SERVER1.username = USER1
SERVER1.key = KEY1

SERVER2.url = <SERVER2_URL>
SERVER2.username = USER2
SERVER2.key = KEY2
# End zanata.ini

Steps to Reproduce:
1. cd <A_ZANATA_PROJECT>
2.  mvn -e zanata:push -Dzanata.url=<SERVER2_URL>  -Dzanata.srcDir=pot


Actual results:
[ERROR] Failed to execute goal org.zanata:zanata-maven-plugin:3.1.2:push (default-cli) on project standalone-pom: Zanata mojo exception: 'SERVER1..url' doesn't map to a class java.net.URL: The value  can't be converted to an URL: no protocol: -> [Help 1]

Expected results:
Invalid URL in SERVER1.url

Additional info:
Comment 1 Ding-Yi Chen 2015-03-22 22:34:18 EDT
Come to think of it, the client did complain about the it cannot read the URL (which is empty).

And it only happened if the invalid entry come before the referred item.
So it seems like an expected behavior.

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