Summary: | Allow Include files to be found relative to the current JMX file | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | Frank Schneider <frankyhro> |
Component: | Main | Assignee: | JMeter issues mailing list <issues> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | hauser, moreira |
Priority: | P2 | ||
Version: | Nightly (Please specify date) | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux | ||
Attachments: | Patch to allow loading files relative to the main jmx file |
Description
Frank Schneider
2007-09-13 12:14:28 UTC
Not a bug. My fault. Start JMeter from Start menue in GNOME so the relative path is not from the bin directory. I am working with version 2.3.4 and I have the same issue. I am using the same JMeter scripts in different machines with different paths to the $JMETER_HOME$/bin directory and also different paths to the scripts. Nevertheless, all scripts are in the same relative path in all machines. So ideally JMeter would make the paths relative to the loaded jmx file so i would not get the Error message: No such file or directory. I saw someone suggesting to simply go to the desired working directory and start the jmeter gui from there. If I am working on different scripts I have to start JMeter every time I change the script. Created attachment 25466 [details]
Patch to allow loading files relative to the main jmx file
Thanks, patch applied: URL: http://svn.apache.org/viewvc?rev=947135&view=rev Log: Bug 43389 - Allow Include files to be found relative to the current JMX file Modified: jakarta/jmeter/trunk/src/components/org/apache/jmeter/control/IncludeController.java jakarta/jmeter/trunk/xdocs/changes.xml jakarta/jmeter/trunk/xdocs/usermanual/component_reference.xml This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2014 |