jmeter paths

[Sergei Riaguzov <ri...@gmail.com>]

Hi!

I'm trying to make Debian package for JMeter from it's binary package
(actually our binary package with extensions and so on) and I'm
thiking about the easiest way to put:

JMeterHome/lib -> /usr/lib
JMeterHome/lib/ext -> /usr/lib/ext

jmeter.properties somewhere into /etc/jmeter and ~/.jmeter.properties
and so on and so forth.

What may be the easiest way for Jmeter to set it's paths if we don't
want to change it's source? I'm thinking about making dummy directory
in tmp with symlinks to all that stuff each time we start JMeter if
there's no such directory there already. Or maybe somewhere in
var/wherever.

Can you point more elegant solution?

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org

Re: jmeter paths

[sebb <se...@gmail.com>]

On 02/08/05, Sergei Riaguzov <ri...@gmail.com> wrote:
> On 8/2/05, sebb <se...@gmail.com> wrote:
> 
> > JMeter looks for its jars and some files relative to the JMeter launch
> > directory.
> > Changing this would require changes to the code (which would need to
> > be backward compatible). But it should be easy enough to provide a
> > command-line property override for the home directory if necessary.
> Ok I see...
> 
> > Most of the files JMeter uses can be shared between users, so it
> > should be possible to put JMeter in /usr/local/jmeter/... and run it
> > from there.
> >
> > The property file path can be provided via a command-line flag, so can
> > be directed to a local file.
> But there's no such property right now, right?

Yes there is - try jmeter -? from the shell:

Error: Unknown option -?
Usage
        -h, --help
                print usage information and exit
        -v, --version
                print the version information and exit
        -p, --propfile <argument>
                the jmeter property file to use
        -q, --addprop <argument>
                additional property file(s)
 [...]

> 
> > What are you trying to achieve?
> Just a Debian package. ;)
> 
> We are going to use JMeter on some amount of machines with Debian, so
> we want to have a package for easy install. Maybe there'll be a CD
> disk with some Testing-with-JMeter-Debian distribution or smth. I am
> not sure for now.
> 
> The other aim is not to change JMeter's code, only our classes which
> are put into /lib/ext, in order to be able to download new version of
> JMeter and use with our plugins later.
> 
> I am just trying to create a more or less "standart" package. :)
> 

But that does not have to go into /usr/lib and /usr/ext, surely?

You may well want to allow for more than one version of JMeter on a
single system, as would be done with java and oracle (for example).

All you then need to do is unpack the archive into the appropriate
directory, define JMETER_HOME to point to the desired installation,
and add JMETER_HOME/bin to the path, or create your own shell script
and put it into /usr/local/bin (e.g.). Try this out and see.

If this does not quite work, there may be some simple enhancements we
can make to JMeter to make the process easier.

S.

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org

Re: jmeter paths

[sebb <se...@gmail.com>]

JMeter looks for its jars and some files relative to the JMeter launch
directory.
Changing this would require changes to the code (which would need to
be backward compatible). But it should be easy enough to provide a
command-line property override for the home directory if necessary.

Most of the files JMeter uses can be shared between users, so it
should be possible to put JMeter in /usr/local/jmeter/... and run it
from there.

The property file path can be provided via a command-line flag, so can
be directed to a local file.

What are you trying to achieve?

S.
On 02/08/05, Sergei Riaguzov <ri...@gmail.com> wrote:
> Hi!
> 
> I'm trying to make Debian package for JMeter from it's binary package
> (actually our binary package with extensions and so on) and I'm
> thiking about the easiest way to put:
> 
> JMeterHome/lib -> /usr/lib
> JMeterHome/lib/ext -> /usr/lib/ext
> 
> jmeter.properties somewhere into /etc/jmeter and ~/.jmeter.properties
> and so on and so forth.
> 
> What may be the easiest way for Jmeter to set it's paths if we don't
> want to change it's source? I'm thinking about making dummy directory
> in tmp with symlinks to all that stuff each time we start JMeter if
> there's no such directory there already. Or maybe somewhere in
> var/wherever.
> 
> Can you point more elegant solution?
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org