Closed joc0611 closed 5 years ago
Thank you @joc0611 for following this through. Looping in @ekerwin to make sure we are on top of things.
AFAICS, the updated hub-common version is already used in master as of 45b6555. Thanks! Do you guys consider this as fixed or should I close the issue once 4.3.0 is publicly available?
Let's close it when 4.3.0 is publicly available, which should be soon.
@ekerwin I think, we have to wait for a version > 4.3.0. I found I bug in my first PR. See https://github.com/blackducksoftware/hub-common/pull/230
@joc0611 we released 4.3.0 and 4.4.0 is code frozen and in QA now. Is the current 4.4.0 branch useful for you?
@akamen https://github.com/blackducksoftware/hub-common/pull/230 over at hub-common will eventually fix this issue. Once the resulting hub-common version is integrated in hub-detect, we can close the issue at hand I guess.
Originally we thought we can close it with the release of 4.3.0, but my initial fix turned out to be incomplete.
I guess we can close this. I successfully tested the fix with version 5.2.0
Expected behavior
BDS_JAVA_HOME
is used to run Signature ScannerActual behavior
scan.cli.zip
is usedSteps to Reproduce
JAVA_HOME
is set,export BDS_JAVA_HOME=${JAVA_HOME}
hub-detect.sh
Version
Project Version: 4.2.1 OS: Alpine Linux
Fix
This is fixed in
hub-common
starting with version 38.2.0, so this issue can be fixed by updating the depency tohub-detect
. Oncehub-common
is released, I can provide a PR if that helps.