Bug 1396395

Summary: Maven should depend on "which"
Product: [Fedora] Fedora Reporter: Bohuslav "Slavek" Kabrda <bkabrda>
Component: javapackages-toolsAssignee: Mikolaj Izdebski <mizdebsk>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: akurtako, java-sig-commits, mat.booth, mizdebsk, msimacek, msrb
Target Milestone: ---Keywords: Upstream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.6.0-15 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1413880 (view as bug list) Environment:
Last Closed: 2016-11-30 10:42:04 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:

Description Bohuslav "Slavek" Kabrda 2016-11-18 09:07:35 UTC
Description of problem:
I have an application that uses maven-invoker to run a maven command. This application runs in a minimal Fedora container, where which is not installed. Since maven-invoker uses /usr/share/maven/bin/mvn and this file contains calls to "which", maven-invoker is unable to run maven, since the script fails.

Version-Release number of selected component (if applicable):
maven-3.3.9-4.fc24.noarch

How reproducible:
Always.

Steps to Reproduce:
1. Create a simple Java app that uses maven-invoker to invoke any maven command.
2. Run it.
3. Observe the failure below.

Actual results:
/usr/share/maven/bin/mvn: line 143: which: command not found
/usr/share/maven/bin/mvn: line 171: which: command not found
Error: JAVA_HOME is not defined correctly.
  We cannot execute 

Expected results:
<no errors>

Additional info:
None.

Comment 1 Mikolaj Izdebski 2016-11-18 09:14:31 UTC
Fixed in javapackages-tools-4.7.0-9

Comment 3 Bohuslav "Slavek" Kabrda 2016-11-18 09:18:14 UTC
Thanks for the quick reaction!

Comment 4 Fedora Update System 2016-11-18 09:33:36 UTC
javapackages-tools-4.7.0-6.1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-ba2b96fc5b

Comment 5 Fedora Update System 2016-11-18 09:34:18 UTC
javapackages-tools-4.6.0-15.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-fcc1da5541

Comment 6 Fedora Update System 2016-11-18 20:26:51 UTC
javapackages-tools-4.7.0-6.1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-ba2b96fc5b

Comment 7 Fedora Update System 2016-11-19 18:50:25 UTC
javapackages-tools-4.6.0-15.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-fcc1da5541

Comment 8 Fedora Update System 2016-11-30 03:52:01 UTC
javapackages-tools-4.6.0-15.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2016-11-30 05:27:28 UTC
javapackages-tools-4.7.0-6.1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 10 Mikolaj Izdebski 2016-11-30 10:42:04 UTC
I believe that this bug is fixed in javapackages-tools-4.6.0-15,
which is available in updates Fedora 24, so I am closing this bug now.

The build containing the fix can be found at Koji:
http://koji.fedoraproject.org/koji/buildinfo?buildID=818652