Bug 1305482 - JAVA path expansion
Summary: JAVA path expansion
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-sdk-java
Version: 3.6.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: ovirt-3.6.3
: ---
Assignee: Juan Hernández
QA Contact: Pavol Brilla
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-08 11:46 UTC by Pavol Brilla
Modified: 2016-02-17 07:33 UTC (History)
8 users (show)

Fixed In Version: rhevm-sdk-java-3.6.2.0-2
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1305871 (view as bug list)
Environment:
Last Closed: 2016-02-17 07:33:05 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pavol Brilla 2016-02-08 11:46:47 UTC
Description of problem:

During erratum run I received:
/usr/src/redhat/BUILD/ovirt-engine-sdk-java-3.6.2.0/generator/regenerate.xml:22: Execute failed: java.io.IOException: Cannot run program "xjc": error=2, No such file or directory


Version-Release number of selected component (if applicable):
rhevm-sdk-java-3.6.2.0-1.el6ev.src.rpm

How reproducible:
100%

Steps to Reproduce:
1.  run ET for rhevm-sdk-java

Actual results:


Expected results:
xjc should be found

Comment 1 Juan Hernández 2016-02-08 11:50:24 UTC
This happens because we assume that the directory /usr/lib/jvm/java-1.8.0-openjdk always exists. But that isn't true, because this is created by the "alternatives" tool, and may not exist in some situations. To avoid this issue we can instead calculate JAVA_HOME like this:

JAVA_HOME=$(dirname $(rpm -ql java-1.8.0-openjdk-devel | grep '/bin$'))

Comment 2 Juan Hernández 2016-02-08 11:51:56 UTC
Pavol, do we need this fixed in order to pass TPS tests, or is there any workaround?

Comment 3 Pavol Brilla 2016-02-09 12:52:08 UTC
Juan, should be fixed, TPS is here to check that we don't need any workarounds

Comment 5 Oved Ourfali 2016-02-11 13:34:59 UTC
Juan - should this be on_qa?

Comment 6 Juan Hernández 2016-02-11 13:40:30 UTC
Yes, it should.

Comment 7 Gil Klein 2016-02-17 07:33:05 UTC
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA


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