Bug 1042892

Summary:	Unable to run CLI: could not load Main class
Product:	[Other] RHQ Project	Reporter:	Libor Zoubek <lzoubek>
Component:	CLI	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	hrupp, lkrejci, theute
Target Milestone:	---
Target Release:	RHQ 4.10
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-04-23 12:30:37 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 Libor Zoubek 2013-12-13 15:02:37 UTC

Description of problem:

Recent commits seem to break CLI at all

Version-Release number of selected component (if applicable):
RHQ 4.10 - master

How reproducible:


Steps to Reproduce:
1. download & run CLI


Actual results:
Error: Could not find or load main class org.rhq.enterprise.client.ClientMain

Expected results:


Additional info:

Comment 1 Lukas Krejci 2013-12-13 16:44:51 UTC

commit b576a5f674fcfd212a1ec62c88314ed7c828b0fd
Author: Lukas Krejci <lkrejci>
Date:   Fri Dec 13 17:39:57 2013 +0100

    [BZ 1042892] Don't use ${} notation for shell variables in CLI scripts.
    
    As of BZ 959603, the files are subject to maven resource filtering and
    so it can happen that the build server passes a variable to the build
    process that clashes with the variable name defined in the script.
    
    (Yes, this actually happened on our Jenkins server that passed
    "-DCLASSPATH=" to the maven process for some reason, which resulted in
    wonderful corruption of the rhq-cli.sh script).

Comment 2 Libor Zoubek 2013-12-16 09:41:56 UTC

verified on RHQ 4.10.0-SNAPSHOT 1b05bf1

Comment 3 Heiko W. Rupp 2014-04-23 12:30:37 UTC

Bulk closing of 4.10 issues.

If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.