Bug 1032201 - Make sure CLI script modules are same on server and CLI zip file
Summary: Make sure CLI script modules are same on server and CLI zip file
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Build System
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: GA
: RHQ 4.10
Assignee: Lukas Krejci
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 1032053
TreeView+ depends on / blocked
 
Reported: 2013-11-19 17:25 UTC by Lukas Krejci
Modified: 2014-04-23 12:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1032053
Environment:
Last Closed: 2014-04-23 12:31:01 UTC
Embargoed:


Attachments (Terms of Use)

Description Lukas Krejci 2013-11-19 17:25:56 UTC
+++ This bug was initially created as a clone of Bug #1032053 +++

Description of problem:

I found out JS samples files serverd by JON server http://$JON_SERVER:7080/downloads/script-modules/ differ from JS samples contained in CLI zip file within /samples/modules (for example jbossas.js)

Version-Release number of selected component (if applicable):
JON 3.2.ER5

How reproducible: always


Steps to Reproduce:
1. download CLI client from server, unzip it
2. download jbossas.js sample module from server
3. compare /samples/modules/jbossas.js from CLI zip with the one you got from server

Actual results: files differ


Expected results: files must be same, the same applies for all other JS modules we ship


Additional info: build process should be fixed and use same source dir for those scripts

Comment 1 Lukas Krejci 2013-11-19 17:32:03 UTC
commit b6fcca7672bb88c72b8835be628a801598bae68d
Author: Lukas Krejci <lkrejci>
Date:   Tue Nov 19 18:31:21 2013 +0100

    [BZ 1032201] - Make sure Server and CLI have the same sample modules

Comment 2 Heiko W. Rupp 2014-04-23 12:31:01 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.


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