Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#33852 - [jmeter] 2.9-1: Unable to access jarfile /usr/bin/ApacheJMeter.jar
Attached to Project:
Community Packages
Opened by Vlalislav (dumphblooz) - Thursday, 14 February 2013, 02:27 GMT
Last edited by Dave Reisner (falconindy) - Friday, 15 February 2013, 13:56 GMT
Opened by Vlalislav (dumphblooz) - Thursday, 14 February 2013, 02:27 GMT
Last edited by Dave Reisner (falconindy) - Friday, 15 February 2013, 13:56 GMT
|
DetailsCan't run jmeter after upgrade to 2.9-1: Unable to access jarfile /usr/bin/ApacheJMeter.jar
|
This task depends upon
Closed by Dave Reisner (falconindy)
Friday, 15 February 2013, 13:56 GMT
Reason for closing: Fixed
Additional comments about closing: community/jmeter-2.9.0-2
Friday, 15 February 2013, 13:56 GMT
Reason for closing: Fixed
Additional comments about closing: community/jmeter-2.9.0-2
/usr/bin/jmeter
$ /usr/bin/jmeter
Error: Unable to access jarfile /usr/bin/ApacheJMeter.jar
From /usr/bin/jmeter:
#! /bin/sh
...
java $ARGS $JVM_ARGS -jar "`dirname "$0"`/ApacheJMeter.jar" "$@"
I always ended up either sed'ing the opt script, making a custom wrapper in /usr/bin, adding the opt-bin path to a profile in /etc/profile.d, etc.
Actually I'm hoping there's a more obvious solution that I'm not aware of.
sed -i '/^java/s|`dirname "$0"`|/opt/jmeter/bin|' "$pkgdir/opt/jmeter/bin/jmeter"