Bug 1025112

Summary: zanata-cli: Incorrect BASE_JARS
Product: [Fedora] Fedora Reporter: Ding-Yi Chen <dchen>
Component: zanata-clientAssignee: Ding-Yi Chen <dchen>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 19CC: dchen, pahuang, rlandman, sflaniga, zanata-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: zanata-client-2.2.0-3.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-10 02:58:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ding-Yi Chen 2013-10-31 03:21:38 UTC
Description of problem:
zanata-cli cannot run with Incorrect BASE_JARS.

Currect: 

BASE_JARS="zanata-rest-client zanata-client-commands zanata-cli slf4j/log4j12 opencsv"

Correct:
BASE_JARS="zanata-client/zanata-rest-client zanata-client/zanata-client-commands zanata-client/zanata-cli slf4j/log4j12 opencsv"

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

How reproducible:
Always

Steps to Reproduce:
1. Run "zanata-cli"

Actual results:
/usr/bin/build-classpath: error: Could not find zanata-rest-client Java extension for this JVM
/usr/bin/build-classpath: error: Could not find zanata-client-commands Java extension for this JVM
/usr/bin/build-classpath: error: Could not find zanata-cli Java extension for this JVM
/usr/bin/build-classpath: error: Some specified jars were not found
Error: Could not find or load main class org.zanata.client.ZanataClient



Expected results:
Show a brief usage page.

Additional info:

Comment 1 Ding-Yi Chen 2014-03-25 23:51:13 UTC
*** Bug 1004136 has been marked as a duplicate of this bug. ***

Comment 2 Sean Flanigan 2014-03-26 00:16:27 UTC
What does CLOSED(NEXTRELEASE) mean for zanata-cli?  I don't think we should use NEXTRELEASE for Zanata.  Or should this bug be reassigned to the Fedora project?

Even if it is a bug in the Fedora package for zanata-cli, we should really fix a bug like this one in fedora-updates, not just the next release.

Comment 3 Sean Flanigan 2014-03-26 00:16:59 UTC
Also, which version actually has the fix?

Comment 4 Ding-Yi Chen 2014-03-26 00:58:11 UTC
For fedora releases, it is recommend to use bodhi and fill the bug number.
After the fix been pushed as stable, it would automatically close the bug and fill in Fix in number.

This was fixed in zanata-client-2.2.0-3.fc19 and zanata-client-2.2.0-3.fc18